@storybook/react 8.1.7 is a minor release of the popular Storybook React renderer, building upon the solid foundation of version 8.1.6. The primary difference lies in the updated dependencies within the Storybook ecosystem. Several internal packages, including @storybook/types, @storybook/docs-tools, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been bumped from version 8.1.6 to 8.1.7 to ensure compatibility and to facilitate bug fixes and feature enhancements to the core framework. These updates likely introduce improvements in areas such as documentation generation, preview rendering, client-side logging, and compatibility with React DOM. While the direct impact on your story writing might be minimal, these internal updates contribute to a smoother and more reliable Storybook experience. The core dependencies and peer dependencies, like React, React DOM, and TypeScript, remain unchanged, ensuring that existing React projects using Storybook can seamlessly upgrade without major compatibility concerns. The release date difference also indicates active maintenance and continuous improvement of the library. Developers can expect that this version incorporates the latest refinements and bug fixes, contributing to a more robust and efficient development workflow, particularly beneficial for larger projects and teams. The untouched fileCount and unpackedSize indicate no significant changes in assets.
All the vulnerabilities related to the version 8.1.7 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.