@storybook/addon-essentials version 7.6.12 introduces subtle yet crucial enhancements compared to its predecessor, version 7.6.11, solidifying its position as a go-to package for streamlining Storybook development. While the core functionality remains consistent, both versions provide a curated suite of add-ons designed to optimize the Storybook experience. These essential add-ons, encompassing tools for documentation (@storybook/addon-docs), interaction testing (@storybook/addon-actions), layout measurement (@storybook/addon-measure, @storybook/addon-outline), UI customization (@storybook/addon-controls, @storybook/addon-toolbars, @storybook/addon-viewport, @storybook/addon-backgrounds), and code highlighting (@storybook/addon-highlight), continue to empower developers to build, test, and showcase UI components effectively.
The primary distinction lies in the internal dependency versions. Version 7.6.12 upgrades all @storybook/* dependencies to their respective 7.6.12 releases. This synchronized update ensures compatibility and potentially incorporates bug fixes or minor improvements within those individual add-ons. Developers benefit from these incremental improvements without needing to manage each add-on separately. Furthermore, both versions share the same peer dependency requirements for React and React-DOM. Developers integrating or updating to the latest addon-essentials should verify that their projects satisfy this peer dependency to ensure an adequate experience with Storybook. Using the latest versions ensures access to the latest features, bug fixes, and performance improvements across the entire Storybook ecosystem.
All the vulnerabilities related to the version 7.6.12 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.