@storybook/react version 7.6.9 is a patch release following version 7.6.8, focusing primarily on internal updates and bug fixes rather than introducing substantial new features. For developers already using Storybook with React, upgrading from 7.6.8 to 7.6.9 should be a straightforward process and is recommended to benefit from the latest stability improvements. Key dependencies like acorn, lodash, and react-element-to-jsx-string remain consistent, ensuring compatibility and a familiar development experience. The peer dependencies, critical for React integration, remain unchanged, supporting React versions 16.8.0 and above including 17 and 18, along with a TypeScript dependency.
The core changes reside within updated internal Storybook packages. Dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 7.6.8 to 7.6.9. Essentially, these upgrades contribute to a more refined and reliable Storybook environment without necessitating significant code alterations in your React components or stories. The devDependencies also saw an update in @storybook/test. Developers looking for the most stable and up-to-date Storybook experience for React projects should update to 7.6.9, as it incorporates bug fixes and refinements within the Storybook core. The release was published on January 17, 2024, a few days after 7.6.8.
All the vulnerabilities related to the version 7.6.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.