@storybook/react version 7.6.13 is a minor release over the previous stable version 7.6.12, primarily focusing on internal dependency updates and bug fixes rather than introducing significant new features for developers. Both versions serve as the React renderer for Storybook, enabling developers to build, test, and showcase UI components in an isolated environment. Analyzing the provided data, the core dependencies and peer dependencies remain largely consistent between the two versions, indicating a stable API and continued support for React versions 16.8.0 through 18.0.0.
The key difference lies in the internal @storybook package versions used as dependencies. Version 7.6.13 updates dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim to their corresponding 7.6.13 versions. These updates likely incorporate bug fixes, performance improvements, and refinements within the Storybook ecosystem. Although not directly exposed to the user, these internal updates contribute to a more robust and reliable Storybook experience. Developers upgrading from 7.6.12 to 7.6.13 can expect a smoother development workflow, benefiting from the accumulated improvements across the Storybook tooling. The upgrade ensures continued compatibility and access to the latest enhancements within the Storybook environment.
All the vulnerabilities related to the version 7.6.13 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.