@storybook/react version 7.0.19 represents a minor update over its predecessor, version 7.0.18, within the Storybook ecosystem for React component development. While appearing largely similar in their core dependencies, including essential tools like Acorn, Lodash, and React-related peer dependencies, the key distinction lies within the versions of Storybook's internal packages. Specifically, dependencies such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been bumped from version 7.0.18 to 7.0.19.
For developers, this signifies a focus on internal improvements, bug fixes, or potentially minor feature additions within the Storybook framework itself, rather than a major overhaul of the React rendering functionality. Upgrading from 7.0.18 to 7.0.19 should be a relatively seamless process, offering enhanced stability, refined documentation capabilities, and potentially better performance in areas like previewing and logging. While no new dependencies are introduced, ensuring alignment with the 7.0.19 versions of Storybook's core packages will guarantee optimal compatibility and unlock the full potential of the Storybook development environment when working with React components. It also contains the most up-to-date bug fixes related to react rendering. Developers should always consider reading the changelog, as these minor version bumps can often contain important security patches.
All the vulnerabilities related to the version 7.0.19 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.