@storybook/react versions 7.0.13 and 7.0.12 are incremental releases of Storybook's React renderer, a crucial part of the Storybook ecosystem that enables developers to build and showcase React components in isolation. Examining the dependencies, core functionalities like rendering, documentation tools and client logging remain consistent between the versions, which both leverage similar versions of core libraries such as acorn, lodash, and react-element-to-jsx-string, as well as peer dependencies for React and React DOM. This indicates a stable core architecture optimized for compatibility with React versions 16.8.0 and above, including versions 17 and 18.
The primary difference lies in the versions of @storybook/* packages. Version 7.0.13 depends on @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim all at version "7.0.13", while version 7.0.12 depends on the same packages at version "7.0.12". These updates likely involve bug fixes, minor feature enhancements, and internal improvements within Storybook's infrastructure. For developers, upgrading to 7.0.13 ensures they benefit from the latest refinements in Storybook's core functionalities, potentially resolving minor issues or improving performance. Consider upgrading to the latest version especially if you rely on any new features.
All the vulnerabilities related to the version 7.0.13 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.