Storybook React has released version 7.6.10, a minor update following closely after 7.6.9. While the core description remains consistent "Storybook React renderer", developers will be interested in the subtle changes under the hood. Examining the dependencies reveals that several Storybook's internal packages have been updated from version 7.6.9 to 7.6.10. This includes @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger and @storybook/react-dom-shim. These updates likely include bug fixes, performance improvements, and potentially new features within Storybook's ecosystem. While the direct impact on React component rendering might be minimal, consistent updates to these packages ensure a smoother and more reliable Storybook experience overall. The developer dependencies also saw a bump with @storybook/test going from 7.6.9 to 7.6.10, which indicates improvements or fixes to the testing utilities provided by Storybook. Finally, fileCount increased from 39 to 39 and unpackedSize from 103530 to 103576, it may be a slight change in the code. Considering the proximity of the releases, upgrading from 7.6.9 to 7.6.10 is recommended to take advantage of these refinements within the Storybook environment.
All the vulnerabilities related to the version 7.6.10 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.