@storybook/react version 7.6.5 introduces subtle but important updates compared to the previous stable release, 7.6.4. While the core functionality remains consistent, several dependency versions have been bumped, primarily within the Storybook ecosystem itself. Key dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been updated from version 7.6.4 to 7.6.5. This suggests internal improvements and bug fixes within Storybook's core components. Additionally, @storybook/test has also been bumped to 7.6.5. Developers relying on Storybook's testing utilities should see potential improvements or fixes related to component testing.
Though most dependency versions remain identical, developers should examine the changelogs for each of the updated @storybook/* packages to understand the precise nature of the changes. This information will help ensure a smooth upgrade and identify any necessary adjustments to their Storybook configurations or component implementations. The update likely includes minor bug fixes, performance enhancements or improvements to the developer experience within the toolchain itself. Given the minor version increment, users can generally expect a straightforward upgrade process without any major breaking changes. Stay informed of the latest features, best practices, and testing improvements for React storybooks.
All the vulnerabilities related to the version 7.6.5 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.