@storybook/react versions 8.1.6 and 8.1.5 are incremental updates to the popular Storybook renderer for React components. Both versions share a core set of dependencies, indicating a consistent foundation for building and showcasing UI components. Key dependencies like react and react-dom as peer dependencies ensure compatibility with a wide range of React versions (16.8.0 up to 19.0.0-beta), giving developers flexibility. The versions also maintain the same development dependencies, including tools for testing and documentation, crucial for a smooth development experience.
The primary difference lies in the version numbers of internal Storybook packages. Version 8.1.6 relies on @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim at version 8.1.6, while version 8.1.5 uses the corresponding 8.1.5 versions. This suggests that the newer release (8.1.6) incorporates bug fixes, performance improvements, or feature enhancements within Storybook's core modules. Developers should consider upgrading to 8.1.6 to benefit from these potential advancements and ensure they are using the most up-to-date and stable release. The updated release date reflects this, with 8.1.6 deployed on June 5, 2024, after 8.1.5 was released on May 30, 2024.
All the vulnerabilities related to the version 8.1.6 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.