The @storybook/addon-essentials package provides a curated set of add-ons designed to enhance the Storybook development experience. Comparing versions 7.0.14 and 7.0.15, the core functionalities remain consistent, both aiming to streamline the process of building and showcasing UI components. Both versions include essential add-ons like actions, controls, docs, measure, outline, toolbars, viewport, highlight, and backgrounds. These tools empower developers to interact with components, document their usage, and fine-tune their appearance across different contexts.
A key observation is the synchronization across the Storybook ecosystem. Version 7.0.15 upgrades the internal dependencies to the 7.0.15 versions of other @storybook/* packages, ensuring compatibility and access to the latest features within the Storybook framework. Similarly, version 7.0.14 uses 7.0.14 versions. Both versions maintain the same peer dependency requirements for React and React DOM, supporting versions 16.8.0 and above, including versions 17 and 18. This broad compatibility allows developers using various React versions to seamlessly integrate the add-on. Additionally, both leverage ts-dedent for cleaner code formatting and include @storybook/vue as a dev dependency, suggesting ongoing support and testing within a Vue.js environment. The updated release date of 7.0.15, about 9 hours after 7.0.14, indicates a quick follow-up release, likely for minor fixes or refinements, reinforcing the stability and ongoing maintenance of @storybook/addon-essentials.
All the vulnerabilities related to the version 7.0.15 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.