@storybook/react version 7.6.4 is a minor release following 7.6.3, primarily focusing on internal dependency updates and refinements to ensure smooth operation within the Storybook ecosystem. While the core functionality of the React renderer remains consistent, developers will notice that several internal Storybook packages, such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim, have been bumped from version 7.6.3 to 7.6.4. These updates likely incorporate bug fixes, performance improvements, or new features within those specific modules, contributing to a more robust and efficient Storybook experience overall.
Developers upgrading from 7.6.3 should anticipate a seamless transition as the public API and core rendering logic are unchanged. The peer dependencies for React and ReactDOM remain the same, supporting versions ^16.8.0, ^17.0.0, and ^18.0.0. TypeScript support also persists. The upgrade's benefits are largely under the hood, providing cumulative enhancements from the updated internal dependencies. If you are already using Storybook 7.6.3 and haven't encountered any issues, upgrading to 7.6.4 is recommended to leverage these subtle yet valuable reliability and performance improvements within the Storybook ecosystem. Keep an eye on the Storybook release notes for detailed breakdowns on the updates to those internal packages.
All the vulnerabilities related to the version 7.6.4 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.