@storybook/react version 8.0.3 represents a small but potentially impactful update over its predecessor, version 8.0.2. As a core component for building UI component libraries and design systems using React, these releases continue the evolution of Storybook.
The primary difference lies in the updated dependencies. Key Storybook packages like @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 8.0.2 to 8.0.3. While a minor version change typically indicates bug fixes and minor feature enhancements, it's crucial for developers to review the changelogs of these individual packages to understand the specific improvements. These changes probably contain fixes and enhanced functionalities for the core modules of storybook. These internal updates can enhance the stability, performance, or developer experience when working with Storybook.
The release date difference indicates rapid iteration and responsiveness to community feedback or identified issues. This rapid release cycle signals an active development team dedicated to providing a robust and reliable experience for react devs building component libraries. Check the official storybook updates and their upgrade guides to have a smooth experience.
Developers should always review the changelogs associated with each Storybook package to fully understand the scope of the updates and potential impact on their projects when upgrading.
All the vulnerabilities related to the version 8.0.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.