@storybook/react version 7.3.0 introduces subtle but potentially impactful changes compared to its predecessor, version 7.2.3. Both versions serve as the React renderer for Storybook, a widely used tool for developing UI components in isolation. The core functionality remains consistent, ensuring developers can continue building and showcasing their React components effectively.
A key difference lies in the updated dependencies. While most dependencies remain at the same versions, several @storybook packages are bumped from 7.2.3 to 7.3.0. Specifically, @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger and @storybook/react-dom-shim are impacted. These updates likely include bug fixes, performance improvements, and new features within the Storybook ecosystem. Although the specific changes within these sub-packages aren't detailed here, developers should consult the Storybook changelog for a comprehensive understanding.
Another notable difference is reflected in the "dist" section. The unpacked size of version 7.3.0 sees a minuscule increase to 479039 bytes from 479025 bytes in version 7.2.3. This suggests underlying code modifications or additions, even if minor. The release date also marks the difference between the versions. Developers are encouraged to upgrade to 7.3.0 to leverage the latest enhancements and fixes, ensuring a smooth and up-to-date Storybook experience for their React component development workflow. Both versions maintain identical peer dependencies, requiring specific React, ReactDOM and Typescript versions for compatibility.
All the vulnerabilities related to the version 7.3.0 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.