Storybook React renderer has released a new version 7.0.4, following closely after the previous 7.0.3. Both versions maintain compatibility with React versions 16.8.0, 17.0.0, and 18.0.0, ensuring a smooth upgrade path for existing projects.
The dependencies remain largely consistent between the two releases, with core utilities like lodash, acorn, and ts-dedent staying at the same versions. Crucially, the internal Storybook packages, such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been updated from version 7.0.3 to 7.0.4. This suggests that the changes in version 7.0.4 are primarily related to improvements and bug fixes within Storybook's core functionalities, potentially affecting the documentation generation, core client interactions, or the preview rendering process. Developers should examine the changelogs for these internal packages to understand the specific changes introduced.
From a developer's perspective, the key takeaway is that version 7.0.4 likely offers a more refined and stable experience compared to 7.0.3, and is a recommended update, especially when using the latest Storybook features. The upgrade ensures access to the newest enhancements and bug fixes within the Storybook ecosystem, contributing to a more reliable and efficient development workflow when building React components and UI systems. The release dates, only 12 hours apart, may suggest a swift resolution to a critical bug found in the previous release, making the upgrade even more urgent.
All the vulnerabilities related to the version 7.0.4 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.