@storybook/react is a powerful library for building UI components in isolation, ideal for React developers seeking a streamlined and efficient workflow. Version 8.1.11 introduces subtle but key updates compared to its predecessor, 8.1.10. While both versions share a robust set of dependencies including core tools like acorn, lodash, semver, and react-element-to-jsx-string, as well as Storybook's internal packages such as @storybook/types, @storybook/docs-tools, @storybook/preview-api, and @storybook/client-logger, the primary distinction lies in the updated versions of Storybook's internal dependencies. Specifically, packages like @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been incremented from version 8.1.10 to 8.1.11.
These updates often incorporate bug fixes, performance enhancements, and new features within the Storybook ecosystem. For developers, this means a potentially more stable and feature-rich environment for creating and showcasing their React components. The peer dependency requirements remain the same, supporting React versions from 16.8.0 onwards, including the latest 19.0.0 beta, ensuring compatibility with a wide range of React projects. Furthermore, both versions maintain the same developer dependencies, like @storybook/test and babel-plugin-react-docgen, which provide tools for testing and documentation generation. Upgrading to 8.1.11 is recommended to take advantage of the latest improvements and ensure compatibility with the evolving Storybook platform.
All the vulnerabilities related to the version 8.1.11 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.