@storybook/addon-essentials is a curated collection of addons designed to enhance the Storybook development experience. Version 7.6.8, released on January 12, 2024, follows closely on the heels of version 7.6.7, released on January 1, 2024. A primary benefit for developers is that upgrading frequently leads to incremental improvements and bug fixes within the familiar Storybook ecosystem. Considering the short time between releases, the changes are likely focused on addressing minor issues or refining existing features rather than introducing major new functionalities. Both versions bundle together essential Storybook addons: Actions, Controls, Docs, Measure, Outline, Toolbars, Viewport, Highlight, and Backgrounds, all at their correspondingly aligned 7.6.x versions. These tools streamline common tasks like inspecting component behavior, adjusting props with interactive controls, generating documentation, and fine-tuning visual aspects.
The dependency lists of both versions illustrate that the core dependencies, including @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, and others, are all updated to their respective 7.6.x versions, ensuring compatibility and access to the latest features within those individual addons. Crucially, the peer dependencies for react and react-dom (^16.8.0 || ^17.0.0 || ^18.0.0) remain consistent, meaning the upgrade shouldn't introduce any compatibility issues with existing React projects using these versions. Developers should consult the Storybook changelog and release notes for a detailed breakdown of the specific fixes and enhancements included in the 7.6.8 release. While the unpacked size and file count remain identical, indicating no significant changes to the overall structure, these smaller releases often contain valuable refinements that contribute to a more stable and user-friendly Storybook environment.
All the vulnerabilities related to the version 7.6.8 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.