Storybook React received a minor update, moving from version 7.2.0 to 7.2.1. While the core functionality and API remain consistent, there are subtle yet important changes to note. Both versions share the same peer dependencies for React, React-DOM, and TypeScript, ensuring compatibility with existing projects using React 16.8.0 or later. Examining the dependencies, most are aligned, but a key difference lies in the versions of internal Storybook packages. Version 7.2.1 updates dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim to their respective 7.2.1 versions, signifying internal bug fixes and synchronization across the Storybook ecosystem. This suggests that version 7.2.1 includes refinements and enhancements within Storybook's core components. For developers, migrating to 7.2.1 is recommended as it likely incorporates crucial bug fixes and stability improvements discovered since the release of 7.2.0. The update strives to provide a smoother and more reliable development experience through its internal package upgrades, even though it won't introduce groundbreaking new features to the component rendering process itself. Users should anticipate improvements to docs generation, core functionalities, and preview rendering. Also, the dist file properties differ, changing the release date, and tarball address.
All the vulnerabilities related to the version 7.2.1 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.