@storybook/react version 7.0.9 is a minor release update to the popular Storybook React renderer, following closely on the heels of version 7.0.8. While the core functionality remains consistent, evidenced by similar dependencies and peer dependencies ensuring compatibility with React versions 16.8.0 through 18.0.0, the update offers refinements and bug fixes that enhance the developer experience. The key difference lies in the internal dependencies of Storybook itself, with several "@storybook/*" packages being bumped from version 7.0.8 to 7.0.9. This suggests improvements within Storybook's core client, preview API, documentation tools, and type definitions, potentially addressing minor issues or incorporating incremental updates.
For developers, upgrading from 7.0.8 to 7.0.9 offers a seamless transition with minimal risk of breaking changes. The update focuses on polishing existing features and ensuring greater stability within the Storybook ecosystem. Although the specific nature of the changes in the updated "@storybook/*" packages are not explicitly detailed in this metadata, users can generally expect improved performance, enhanced reliability, and potentially subtle enhancements to the documentation rendering or Storybook's overall development workflow. The release date of 7.0.9, just two days after 7.0.8, signifies a rapid response to issues or introduction of quick fixes, making it a recommended upgrade for users seeking the most up-to-date and refined experience with Storybook for React.
All the vulnerabilities related to the version 7.0.9 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.