@storybook/react version 7.6.18 introduces subtle yet important updates compared to its predecessor, 7.6.17. The primary difference lies in the updated dependencies, specifically within the @storybook ecosystem. The core packages like "@storybook/types," "@storybook/docs-tools," "@storybook/core-client," "@storybook/preview-api," "@storybook/client-logger," and "@storybook/react-dom-shim" have all been bumped from version 7.6.17 to 7.6.18.
These updates likely encompass bug fixes, performance improvements, and potentially new features within those individual packages. While the direct dependencies of core packages usually don't cause breaking changes it's a good practice to bump all the Storybook related packages every time you upgrade. Developers leveraging Storybook for React should consider upgrading to the latest version (7.6.18) to benefit from these enhancements and fixes.
The peer dependencies remain unchanged, ensuring compatibility with React versions 16.8.0 and above, including versions 17 and 18, along with requiring TypeScript. The file size and overall structure appear consistent between the two releases, suggesting that the focus was on internal improvements and refinements rather than major architectural changes. The release date difference indicates active maintenance and ongoing development of the Storybook ecosystem, reinforcing it as a robust and actively supported tool for React component development and testing. The most recent release happened on April 23, 2024.
All the vulnerabilities related to the version 7.6.18 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.