@storybook/react version 7.5.3 represents a minor update to the popular Storybook React renderer, building upon the foundation laid by version 7.5.2. This release, published on November 6, 2023, follows the previous version released on October 30, 2023. While the core dependencies like React, React DOM, and TypeScript remain within the same peer dependency constraints, ensuring compatibility across a wide range of React projects (v16.8.0 to v18.0.0), subtle changes under the hood contribute to an improved development experience.
A key area of focus in this update seems to be the alignment of internal Storybook packages. The dependencies on @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 7.5.2 to 7.5.3. This synchronization typically indicates bug fixes, performance enhancements, or new features within Storybook's internal ecosystem, which indirectly benefit React developers using the renderer. Developers should expect smoother interactions with Storybook's core functionalities, improved documentation generation, and potentially performance gains when rendering React components within the Storybook environment. While seemingly a smaller release, this version ensures developers are using the most up-to-date and cohesive set of Storybook tools for their React component development and testing workflows. The unpacked size and file count remain the same, suggesting the changes are primarily internal refinements rather than large-scale additions. This makes upgrading a low-risk operation with potential for subtle but valuable improvements.
All the vulnerabilities related to the version 7.5.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.