The @storybook/addon-essentials package provides a curated set of Storybook addons designed to enhance the development and testing workflow. Version 7.6.7 was released on January 1, 2024, following version 7.6.6, released on December 19, 2023. Both versions share the same core functionality, delivering essential tools like Docs, Actions, Measure, Outline, Controls, Toolbars, Viewport, Highlight, and Backgrounds addons.
The key distinction lies in the updated dependencies within version 7.6.7. Each essential addon, such as @storybook/addon-docs, @storybook/addon-actions, and others, has been bumped to version 7.6.7, aligning them with the latest core Storybook release. This synchronization ensures compatibility and potentially introduces bug fixes or minor feature enhancements across the board.
For developers, this means upgrading to version 7.6.7 primarily involves ensuring that all Storybook-related packages are on the same version. The consistent versioning across the addon-essentials and its dependencies simplifies dependency management and reduces the risk of version conflicts. While the core functionality remains the same, developers benefit from any incremental improvements or fixes incorporated into those individual addons by upgrading to the latest version. This update is especially important for developers working on newer projects or those aiming to maintain the most up-to-date Storybook environment, ensuring they leverage the latest features and stability improvements across the Storybook ecosystem.
All the vulnerabilities related to the version 7.6.7 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.