@storybook/react version 8.0.7 represents a minor iteration over the previous stable release, 8.0.6, continuing to refine the Storybook experience for React developers. While the core dependencies remain largely consistent, subtle version bumps indicate underlying improvements and bug fixes. Notably, dependencies like @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are updated to 8.0.7, aligning them with the latest Storybook ecosystem components.
Developers migrating from 8.0.6 should anticipate incremental enhancements rather than breaking changes. The focus remains on robust support for React versions 16.8.0 through 18.0.0, as indicated by the peer dependencies. The consistent use of development dependencies, including testing utilities and type definitions, underscores a commitment to code quality and developer tooling.
The upgrade to 8.0.7 is recommended for users seeking the most up-to-date features and stability improvements within the Storybook React renderer. Examining the commit history between these versions will reveal specific fixes and enhancements relevant to individual project needs. The unchanged file count and unpacked size suggests minimal code changes, implying that the update primarily addresses internal refinements and dependency synchronization within the Storybook framework which could benefit React projects using Storybook for UI component development and testing.
All the vulnerabilities related to the version 8.0.7 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.