Storybook React has released version 7.0.5, a minor update following closely on the heels of version 7.0.4. Both versions are focused on rendering React components within the Storybook environment. Examining the package data, the core functionalities and dependencies remain largely consistent between the two releases. The dependencies like acorn, lodash, react-element-to-jsx-string, and Storybook's internal packages (@storybook/types, @storybook/global, @storybook/docs-tools, etc.) show no obvious version bumps, suggesting a focus on internal fixes or minor adjustments rather than significant feature additions. The peer dependencies for react and react-dom are also unchanged, ensuring compatibility with React versions 16.8.0 through 18.0.0.
Developers should note the subtle differences mainly reside within the internal Storybook packages (e.g., @storybook/types, @storybook/core-client). This kind of point release typically indicates bug fixes, performance improvements, or refinements to existing features within the Storybook ecosystem. Although the unpacked and file count are identical, the key difference lies in the release dates, indicating that 7.0.5 incorporates changes deployed after 7.0.4, most probably resolving issues identified in the previous release. For users of Storybook React, upgrading to 7.0.5 is generally recommended to benefit from these potential stability and performance enhancements. While the change log from version 7.0.4 to 7.0.5 will give an accurate picture of the changes between the two versions, the upgrade effort will typically be minimal.
All the vulnerabilities related to the version 7.0.5 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.