@storybook/react version 7.3.1 is a minor release following 7.3.0, providing enhancements and potential bug fixes to the popular Storybook React renderer. Both versions share the same core dependencies, including tools like acorn, lodash, and escodegen for JavaScript parsing and code generation. Key dependencies like @storybook/types, @storybook/global, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are crucial parts of the Storybook ecosystem, driving its functionality. Notably, version 7.3.1 updates most of these internal Storybook packages to 7.3.1 from 7.3.0 in the earlier version, suggesting internal synchronisation. The react-element-to-jsx-stringdependency remains unchanged.
Developer dependencies for testing and tooling also remain largely constant. One can assume that these recent releases ensure better compatibility with React versions 16.8.0, 17.0.0, and 18.0.0 given the peer dependency specifications are identical. For developers, upgrading from 7.3.0 to 7.3.1 should be straightforward. Although a minor update, it's always recommended to check the Storybook release notes for specific fixes or improvements that might impact your project. These incremental releases often address edge cases which improve stability to the library and address specific issues promptly. Consider release dates as well, there is only a day difference between them which means that most probably the newest release includes a fix for a bug found on the previous one.
All the vulnerabilities related to the version 7.3.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.