@storybook/react version 7.0.11 represents a minor update over the previous stable version, 7.0.10, focusing on internal dependency synchronization and potential bug fixes. While the core functionality remains consistent, developers should note the subtle shifts in sub-package versions. Specifically, dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been bumped from version 7.0.10 to 7.0.11 to align with the main package version. These updates likely incorporate small improvements, bug resolutions, or refinements within Storybook's ecosystem.
For developers already using @storybook/react, upgrading to 7.0.11 is generally recommended to benefit from the latest enhancements and resolved issues across Storybook's internal modules. This upgrade ensures better compatibility and stability within the Storybook environment. Reviewing the changelogs for impacted sub-packages might provide more granular insights, but the primary focus of the update is internal consistency. Both versions maintain the same peer dependency requirements for React and React DOM, indicating no breaking changes related to core React usage. The consistent file count and unpacked size suggest that the update primarily addresses code within existing files rather than adding significant new features or assets. The release date difference highlights the active development and maintenance within the Storybook project.
All the vulnerabilities related to the version 7.0.11 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.