The @storybook/react package provides the React renderer for Storybook, a popular tool for building UI components in isolation. Version 7.6.20 is a recent update to this package, released on June 24, 2024, following version 7.6.19 released on May 1, 2024. While both versions share the same core dependencies like acorn, lodash, and react-element-to-jsx-string, the key difference lies in the updated versions of Storybook's internal packages. Specifically, @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are all bumped from 7.6.19 to 7.6.20 in the newer release.
For developers, this likely translates to bug fixes, performance improvements, and potentially new features within Storybook's core functionalities related to documentation, core client interactions, previewing components, logging, and React DOM interactions. The peer dependencies remain consistent, ensuring compatibility with React versions 16.8.0 and up, including versions 17 and 18, as well as requiring TypeScript. These updates aim to improve the overall Storybook experience, ensuring a smoother and more efficient workflow for building robust and well-documented React components. While the file count and unpacked size are the same between the two versions, the internal dependency updates usually reflect refinements that contribute to a more stable and feature-rich environment for React component development within Storybook.
All the vulnerabilities related to the version 7.6.20 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.