@storybook/react, a popular library for building UI components in isolation within a React environment, has released version 7.2.3 following closely on the heels of 7.2.2. Both versions share the same core functionalities, providing developers with tools to efficiently develop, test, and showcase React components. The description field remains consistent: "Storybook React renderer", indicating that both versions focus primarily on rendering React components within the Storybook environment.
A subtle yet important difference lies within the dependencies section. While the majority of dependency versions remain the same, the @storybook-related packages (@storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, @storybook/react-dom-shim) have been bumped up from version 7.2.2 to 7.2.3. This suggests that the update primarily involves internal bug fixes, performance improvements, and alignment within the Storybook ecosystem rather than introducing a full overhaul.
For developers, this implies a smooth transition when upgrading. While new features might not be prominent, the updated dependencies likely bring enhanced stability and compatibility across the Storybook platform. Keeping track of these minor version bumps ensures that developers are leveraging the latest refinements from the Storybook team, benefiting from improved reliability and a more consistent development experience. Notably, the peerDependencies remain consistent, ensuring compatibility with React versions 16.8.0, 17.0.0, and 18.0.0, as well as TypeScript projects. The release date indicates a recent update, with version 7.2.3 being released just two days after 7.2.2.
All the vulnerabilities related to the version 7.2.3 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.