@storybook/react version 7.0.2 is a minor release following 7.0.1, focusing on incremental improvements and bug fixes for the Storybook React renderer. Both versions are designed to offer a streamlined and efficient environment for building and testing React components in isolation. Key dependencies remain consistent between the two versions, ensuring a stable development experience with libraries like acorn, lodash, react-element-to-jsx-string, and various Storybook internal packages such as @storybook/types, @storybook/docs-tools, @storybook/core-client, and @storybook/preview-api. Developers can continue to leverage these dependencies with confidence.
The peer dependencies for both versions remain unchanged, requiring React and React DOM versions ^16.8.0, ^17.0.0, or ^18.0.0, ensuring compatibility with a wide range of React projects. Development dependencies like typescript, @babel/core, expect-type, require-from-string, and jest-specific-snapshot are also consistent, indicating a focus on maintaining a stable development and testing pipeline.
The primary distinction lies in the internal updates reflected in the @storybook/* dependency versions. While the core functionality and API remain largely the same, version 7.0.2 likely incorporates fixes and enhancements discovered since the release of 7.0.1. The release dates, a few hours apart, suggest a hotfix or quick follow-up to address immediate issues. Upgrading from 7.0.1 to 7.0.2 is recommended to benefit from the latest refinements and ensure optimal stability within the Storybook environment.
All the vulnerabilities related to the version 7.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.