Version 7.0.8 of @storybook/react introduces subtle yet important enhancements over its predecessor, version 7.0.7, focusing on refinements and internal dependency updates. While the core functionality of rendering React components within Storybook remains consistent, developers should be aware of the changes in dependency versions. Specifically, key @storybook dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been updated from 7.0.7 to 7.0.8. These internal updates likely contain bug fixes, performance improvements, and potentially new features within the Storybook ecosystem itself. Although no breaking changes are explicitly highlighted, developers are encouraged to review the changelogs for these individual @storybook packages to understand the precise nature of the updates.
Furthermore, the dist metadata reveals minor alterations: the fileCount has slightly decreased from 186 to 184 and the unpackedSize has also slightly reduced from 477297 to 475433. These suggest optimizations in the package's structure. Finally, the "directory" field within the "repository" section has been updated from renderers/react to code/renderers/react, meaning that the location of the sources inside the repository has changed.
For developers, upgrading to 7.0.8 offers the benefit of staying current with the Storybook ecosystem, leveraging any improvements and fixes included in the dependency updates. This incremental update approach is generally recommended for maintaining a stable and performant Storybook environment.
All the vulnerabilities related to the version 7.0.8 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.