@storybook/react version 7.6.14 is a patch update to the popular Storybook React renderer, building upon the foundation of the 7.6.x series. Comparing it to the previous version, 7.6.13, the core functionalities and peer dependencies remain consistent (React ^16.8.0 || ^17.0.0 || ^18.0.0 and React-DOM ^16.8.0 || ^17.0.0 || ^18.0.0). This ensures a smooth transition for developers already using Storybook with React.
The most notable difference lies in the updated dependencies. Packages like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, @storybook/react-dom-shim and @storybook/test have been bumped from version 7.6.13 to 7.6.14 to maintain consistency across the Storybook ecosystem. While the specific changes within these sub-packages aren't detailed here, patch releases typically include bug fixes, performance improvements, and minor enhancements that contribute to a more stable and refined development experience.
Developers upgrading from 7.6.13 should expect a seamless transition, potentially benefiting from under-the-hood improvements within Storybook's core modules, related to documentation, testing, or client-side functionalities. The upgrade ensures alignment with the latest advancements in the Storybook ecosystem, streamlining component development and showcasing, leading to richer documentation and more robust React applications.
All the vulnerabilities related to the version 7.6.14 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.