Storybook React renderer has been updated from version 7.0.9 to 7.0.10, offering subtle refinements and improvements for developers leveraging React within the Storybook environment. Both versions maintain identical core dependencies and functionalities, including essential tools like acorn, lodash, escodegen, and ts-dedent. Key Storybook components such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are also consistently present, ensuring a stable and familiar development experience. The peer dependencies for react and react-dom remain unchanged, supporting versions 16.8.0, 17.0.0, and 18.0.0.
The primary distinction lies in the updated versions of internal Storybook packages to align with the 7.0.10 release cycle. While the listed dependencies and devDependencies show no significant changes in their specified version ranges, the core update ensures better consistency and potentially includes bug fixes or minor enhancements within the Storybook ecosystem. The unpackedSize increased marginally, suggesting slight adjustments or additions in the core files. Developers should update to version 7.0.10 for the most current bug fixes and optimized integrations within the broader Storybook platform, ensuring smooth operation and compatibility with other Storybook packages.
All the vulnerabilities related to the version 7.0.10 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.