@storybook/react version 7.6.2 represents a minor update over its predecessor, version 7.6.1, primarily focusing on internal dependency upgrades and bug fixes. While the core API and functionality remain consistent, developers will experience subtle improvements in stability and performance. A key takeaway is that several @storybook dependencies, like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim, have been bumped from 7.6.1 to 7.6.2, ensuring a more cohesive and synchronized ecosystem.
The update provides a refined and dependable platform for building UI components in isolation. Existing projects using Storybook 7.6.1 can likely upgrade to 7.6.2 without significant code modifications, making the transition smooth and straightforward. This minimizes disruption and lets developers immediately benefit from the improvements. This release continues to support React versions 16.8.0, 17.0.0, and 18.0.0, guaranteeing broad compatibility across diverse project setups. TypeScript support remains robust, solidifying Storybook's role in modern JavaScript development workflows. Developers should always prioritize staying current with the latest minor versions to capitalize on bug fixes and performance enhancements. The core dependencies like react, react-dom, typescript, acorn, lodash, and others remain untouched between the two versions.
All the vulnerabilities related to the version 7.6.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.