@storybook/react saw a minor version bump from 7.6.0 to 7.6.1, offering subtle but important updates for React component development and documentation within Storybook. Both versions maintain the same core dependencies like acorn, lodash, and peer dependencies for react and react-dom ensuring compatibility with your existing React projects (v16.8.0 and later). Developers should note that both versions explicitly declare support for react versions 16, 17 and 18.
The key difference lies in the updated internal dependencies: @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, @storybook/react-dom-shim, and @storybook/test all incremented from version 7.6.0 to 7.6.1. This signifies improvements and bug fixes within Storybook's core functionalities impacting type definitions, documentation generation, core client interactions, preview functionalities, logging, React DOM shims, and testing utilities. While the changes might not introduce new features directly visible in your code, they enhance the stability and reliability of the Storybook environment. Upgrading to 7.6.1 provides developers with a more refined and robust experience, particularly beneficial for larger projects where subtle improvements can have a significant impact on performance and maintainability. The absence of breaking changes in dependencies suggests a smooth upgrade path.
All the vulnerabilities related to the version 7.6.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.