@storybook/react saw a minor version update from 8.0.0 to 8.0.1, released on March 18, 2024. While both versions maintain the core functionality of rendering React components within the Storybook environment, a few key differences are worth noting for developers. The most immediate change lies in the updated dependencies. Several internal Storybook packages, including @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim, were bumped from version 8.0.0 to 8.0.1. This suggests bug fixes, performance improvements, or minor feature additions within these internal modules that collectively enhance the React renderer. Developers should expect a more stable and refined experience when upgrading.
Importantly, the peer dependencies – react, react-dom, and typescript – remain consistent, ensuring compatibility for existing projects. The core dependencies, such as acorn, lodash, and semver, also remain unchanged, indicating a focus on incremental improvements rather than fundamental architectural shifts. While the unpacked size and file count remain the same, which confirms that the update is small and doesn't add a lot of new features, using the latest 8.0.1 version gives to the developers the peace of mind of using an updated version and will grant them access to the latest patches and stability improvements within the Storybook ecosystem for React. As always, reviewing the official Storybook changelog for detailed release notes is recommended before upgrading.
All the vulnerabilities related to the version 8.0.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.