@storybook/react version 8.1.9 introduces subtle but important updates compared to its predecessor, 8.1.8. While the core functionality remains consistent, several dependency versions have been bumped within Storybook's internal ecosystem. Specifically, dependencies like @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been updated from version 8.1.8 to 8.1.9. These internal package updates likely incorporate bug fixes, performance improvements, and refinements to enhance the overall Storybook experience for React developers.
Developers upgrading to 8.1.9 can anticipate a smoother and more reliable environment for building and showcasing their React components. Though specific details of the internal changes aren't explicitly outlined, the updates suggest a focus on refining the developer experience within the Storybook ecosystem. Other dependencies and devDependencies remain untouched between the versions. The unpacked package size and file count stay the same, probably meaning that the changes are minimal. Crucially, the peer dependencies for React, React DOM, and TypeScript remain unchanged, ensuring compatibility with existing project setups. For users already on the Storybook 8.x series, this upgrade should be relatively straightforward, promising incremental improvements without introducing major breaking changes. The new version was released just 14 hours after the older one.
All the vulnerabilities related to the version 8.1.9 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.