@storybook/react version 7.0.12 is a minor release following 7.0.11, offering enhancements and refinements to the Storybook React renderer. Both versions maintain the core functionality of rendering React components within the Storybook environment, empowering developers to build, test, and showcase UI components in isolation. Key dependencies like acorn, lodash, escodegen, and prop-types remain consistent, ensuring familiar behavior and compatibility. The peer dependencies specify React and React DOM versions ^16.8.0, ^17.0.0, or ^18.0.0, reinforcing the library's support across a broad range of React versions. Although, the dependencies @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, @storybook/react-dom-shim has been bumped from 7.0.11 to 7.0.12. The @storybook/global dependency remains static on version 5.0.0. From a developer perspective, updating from 7.0.11 to 7.0.12 should present minimal disruption, focusing on incremental improvements and bug fixes rather than significant API changes. This approach ensures a smooth upgrade experience, allowing teams to rapidly adopt the latest enhancements without extensive code modifications. The small size difference in unpacked size suggests minor code adjustments or asset updates containted in the newest versions of the dependencies. To benefit from the latest improvements developers should update dependencies accordingly..
All the vulnerabilities related to the version 7.0.12 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.