@storybook/react version 7.4.3 represents a minor update over the previous stable version, 7.4.2, primarily focusing on internal dependency alignment and bug fixes, contributing to a more robust and consistent development experience. The core functionality and API remain largely the same, allowing developers to upgrade seamlessly without significant code changes. Diving into the specifics, a key difference lies in the updated versions of Storybook's internal packages, such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim. These updates likely incorporate bug fixes, performance improvements, and internal enhancements that contribute to the overall stability and efficiency of the React renderer. The update doesn't introduce new features that would drastically alter the development workflow, but improves the existing features. For developers, version 7.4.3 offers a refined experience with enhanced reliability. While the changes are not groundbreaking, maintaining up-to-date packages like Storybook ensures access to the latest bug fixes and improvements that contribute to a smoother development process. Users are encouraged to upgrade to version 7.4.3 for a slightly better, consistent, and reliable experience in their day-to-day work with React Storybook.
All the vulnerabilities related to the version 7.4.3 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.