@storybook/react versions 7.0.24 and 7.0.23 represent incremental updates to the popular Storybook renderer for React components. Examining the differences, developers will primarily notice version bumps across Storybook's internal dependencies. In version 7.0.24, key packages such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are all updated to 7.0.24, aligning them with the core package version. These updates likely include bug fixes, performance improvements, and potentially new features within Storybook's ecosystem that enhance the developer experience when building and showcasing React components.
The update from 7.0.23 to 7.0.24 doesn't introduce any breaking changes as far as direct dependencies or peer dependencies are concerned, making the upgrade smooth and straightforward. While the core dependencies are seeing updates, the peer dependencies remain constant with react and react-dom versions ^16.8.0 || ^17.0.0 || ^18.0.0. Developers benefit through a more stable and feature-rich Storybook environment for React. By aligning internal versions, Storybook ensures consistency and reduces the risk of compatibility issues. Ultimately, developers should upgrade to 7.0.24 to leverage the latest enhancements and maintain an up-to-date Storybook instance for their React projects.
All the vulnerabilities related to the version 7.0.24 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.