@storybook/react version 7.6.6 represents a minor update to the Storybook React renderer, building upon the foundation laid by version 7.6.5. Analyzing the package data, the primary difference lies in the version numbers of its internal dependencies, particularly those under the @storybook namespace. For instance, 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.6.5 to 7.6.6.
These updates likely incorporate bug fixes, performance improvements, and potentially new features within Storybook's core functionalities, enhancing the overall development experience. While the direct impact of these changes might not be immediately apparent on the surface, they contribute to a more stable and robust Storybook environment. Developers using @storybook/react should consider upgrading to this latest version to benefit from the aggregated improvements and ensure compatibility with the broader Storybook ecosystem.
Furthermore, examining the releaseDate indicates that version 7.6.6 was released a few days after 7.6.5, suggesting that the changes included are likely targeted fixes or immediate enhancements identified post-release of the earlier version. The core dependencies and devDependencies remain mostly consistent, indicating no drastic architectural shifts between the releases. Thus, the upgrade poses a low risk of breaking existing setups while providing access to the newest refinements.
All the vulnerabilities related to the version 7.6.6 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.