@storybook/react version 7.0.20 represents a minor update over its predecessor, version 7.0.19, primarily focusing on internal dependency synchronization within the Storybook ecosystem. The core functionality for rendering React components remains consistent, ensuring a smooth transition for developers already using Storybook. Key dependencies like acorn, lodash, acorn-jsx, and escodegen remain at the same versions, indicating no significant changes in core Javascript processing or component rendering logic.
The update mainly involves aligning the @storybook/* packages to version 7.0.20, including @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim. This synchronization signals an effort to ensure compatibility and stability across the Storybook suite of tools. Although seemingly minor, such synchronization is crucial for preventing potential conflicts and ensuring that features across different Storybook modules operate as expected.
Developers leveraging @storybook/react will find that upgrading from 7.0.19 to 7.0.20 introduces no breaking changes in terms of API or core rendering behavior. The peer dependencies for react and react-dom remain consistent, supporting versions 16.8.0, 17.0.0, and 18.0.0. The developer tooling, including TypeScript, Babel, and testing libraries, also remains unchanged, suggesting that the main focus was on internal consistency rather than the introduction of new features or significant code refactoring. The release dates of the two versions, being a very small time apart, further emphasis this point.
All the vulnerabilities related to the version 7.0.20 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.