Storybook React has released version 8.1.10, a minor update following version 8.1.9. Both versions serve as renderers for React components within the Storybook environment, enabling developers to build, test, and showcase UI components in isolation. Key dependencies like React, React-DOM, and TypeScript remain consistent, ensuring compatibility with a wide range of React projects. Developers will find core utilities such as acorn for JavaScript parsing, lodash for utility functions, and semver for version management unchanged, maintaining stability across the update. The peer dependencies remain the same, so the impact should be minimal for most users.
The update introduces subtle refinements, primarily reflected in the @storybook/* packages. For example, @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 8.1.9 to 8.1.10. These internal package updates likely contain bug fixes, performance improvements, or minor feature enhancements that contribute to a more polished Storybook experience. While specific details of these changes aren't explicitly outlined, developers can generally expect improved reliability and potentially enhanced rendering capabilities. From the information provided it is hard to see significant changes as the unpacked size of the package only increased slightly, but as always it is recommended to review the changelogs of the updated packages for detailed information, and test the update in a non-production environment before deploying to production.
All the vulnerabilities related to the version 8.1.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.