@storybook/addon-essentials versions 8.0.9 and 8.0.8, provide a curated suite of add-ons designed to enhance the Storybook development experience. Both versions aim to streamline the creation and presentation of UI components. Crucially, the primary difference lies in their release dates and the versions of their dependent packages. Version 8.0.9 was released on April 22, 2024, while version 8.0.8 was released on April 11, 2024, indicating bug fixes or minor feature enhancements are more than likely the driver to create the new release.
Both versions share the same core set of dependencies signifying a stable API and feature set. These include essential add-ons like @storybook/addon-docs for documentation, @storybook/addon-controls for interactive component property manipulation, @storybook/addon-actions for recording user interactions, and other fundamental utilities like @storybook/addon-viewport, @storybook/addon-backgrounds, @storybook/addon-highlight, @storybook/addon-outline, @storybook/addon-measure and @storybook/addon-toolbars. Developers can expect a consistent and reliable set of tools for building, testing, and showcasing their UI components in an isolated environment. The consistent dependency versions between the two versions provides confidence for upgrading, as any upgrade would likely be low risk.
For developers looking to adopt or upgrade, consider the release date: version 8.0.9 includes the latest bug fixes and refinements. Always refer to the official Storybook changelog for a comprehensive list of changes; the changelog will provide detailed insights into the specific updates included in version 8.0.9.
All the vulnerabilities related to the version 8.0.9 of the package
Cross site scripting in markdown-to-jsx
Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: *
header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com
).fetch('http://127.0.0.1:8000/main.js')
request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js
.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html
: normally you have a script tag here/assets
: it's common to have a assets
directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild
SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data))
)The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm i
npm run watch
fetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content))
in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.