@storybook/react has a new release, version 8.1.3, arriving just a few days after version 8.1.2. Both versions focus on providing a robust React renderer for Storybook, a popular tool for building UI components in isolation. Examining the metadata, the core functionality and feature set seem largely consistent between the two releases.
The key difference between 8.1.3 and 8.1.2 appears to be in the internal versioning of Storybook's core packages. The dependencies like @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are bumped from 8.1.2 to 8.1.3 reflecting internal updates and synchronization within the Storybook ecosystem. The dependency @storybook/test is also updated to 8.1.3.
For developers already using @storybook/react, upgrading from 8.1.2 to 8.1.3 is likely a straightforward process, aiming to benefit from the latest bug fixes, and internal improvements within the Storybook platform. No breaking API changes are indicated by the provided data, but still recommended to check the release notes.
Both versions share the same peer dependencies (react, react-dom, and typescript), ensuring compatibility with a wide range of React projects.
All the vulnerabilities related to the version 8.1.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.