@storybook/react versions 7.0.0 and 7.0.1 represent incremental improvements to the popular React renderer for Storybook, a powerful tool for UI development and testing. While both versions share the same core dependencies like React, React DOM, and various utilities such as lodash, acorn, and escodegen, the key distinctions lie in their internal Storybook package dependencies. Version 7.0.1 updates internal dependencies such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim to version 7.0.1, aligning them with the overall Storybook ecosystem. In contrast, version 7.0.0 relies on version 7.0.0 of these internal packages.
For developers, this means that upgrading from 7.0.0 to 7.0.1 ensures they are leveraging the latest refinements and bug fixes within the Storybook framework. Although the changes might not introduce major new features directly visible in the React rendering, this upgrade standardizes the interconnected Storybook packages. This results in a more stable and predictable development experience. Furthermore, developers can use the newest tools and improvements with other storybook core packages that are only available in the newest version, resulting in increased performance and compatibility. The patch release optimizes the Storybook environment.
All the vulnerabilities related to the version 7.0.1 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.