@storybook/addon-essentials version 7.4.1 is a minor release over version 7.4.0, offering a refined set of pre-packaged Storybook addons designed to enhance the development workflow and user experience. Both versions provide developers with a curated collection including essential tools for documentation, interactivity, and visual debugging. Key addons bundled within include Actions for logging interactions, Controls for dynamic component property modification, Docs for automated documentation generation, Viewport to simulate different screen sizes and Measure/Outline/Backgrounds addons for precise visual adjustments.
The primary difference lies in the updated dependencies within version 7.4.1. Each addon within @storybook/addon-essentials, such as @storybook/addon-docs, @storybook/addon-controls, and others, is bumped to version 7.4.1 to ensure consistency within the Storybook ecosystem. This synchronization usually indicates bug fixes or incremental improvements across all first-party addons, promoting stability and optimized interoperability. For developers, upgrading to 7.4.1 means benefiting from the latest enhancements and fixes present throughout the entire suite of essential addons, streamlining their Storybook experience. Therefore, users are recommended to upgrade to version 7.4.1 to leverage the most up-to-date features.
All the vulnerabilities related to the version 7.4.1 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.