@storybook/addon-essentials is a curated set of add-ons designed to enhance the Storybook development experience by providing essential tools and features. Version 7.4.3 builds upon the foundation laid by version 7.4.2, offering subtle improvements and refinements for Storybook users.
The core functionality remains consistent between the two versions, with both including vital add-ons like @storybook/addon-docs for documentation, @storybook/addon-controls for interactive story modification, and various other tools for actions, measuring, outlining, toolbars, viewports, highlighting, and background customization. These add-ons work together to streamline the UI development workflow, allowing developers to create, test, and document their components effectively within Storybook.
While the dependency lists appear very similar, with shared dependencies like ts-dedent, the key difference lies in the version numbers of the internal Storybook packages. Each add-on dependency in version 7.4.3 is updated to its corresponding 7.4.3 version, ensuring compatibility and potentially incorporating bug fixes or minor feature enhancements released within those individual add-ons since version 7.4.2. This synchronization of internal dependencies ensures everything works seamlessly together. Developers upgrading from 7.4.2 to 7.4.3 can expect a smoother and potentially more stable experience due to these incremental updates. Upgrading is generally recommended to benefit from the latest bug fixes and improvements within the Storybook ecosystem.
All the vulnerabilities related to the version 7.4.3 of the package
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 inpm run watchfetch('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.