@storybook/react version 8.0.2 is a minor update to the Storybook React renderer, released shortly after version 8.0.1. Upgrading from 8.0.1 to 8.0.2 mainly involves getting the latest fixes and improvements within the Storybook ecosystem.
While the core dependencies remain largely the same, the key difference lies in the updated versions of internal Storybook packages. Notably, dependencies such as @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 8.0.1 to 8.0.2. These updates likely contain bug fixes, performance enhancements, and potentially new features that enhance the overall Storybook development experience.
Developers should consider upgrading to 8.0.2 to benefit from the most recent stabilization efforts and ensure compatibility with the latest Storybook features. The peer dependencies for React, React DOM, and TypeScript remain unchanged, so the upgrade should be straightforward for most projects already using Storybook 8.x. It's always a good practice to review the changelog for the Storybook monorepo to understand the specific changes included in these minor version bumps, ensuring a smooth transition and taking advantage of any new capabilities. This version also incorporates fixes in areas like documentation generation, preview handling, logging, and the React DOM shim, contributing towards a more polished Storybook experience overall.
All the vulnerabilities related to the version 8.0.2 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.