@storybook/react version 7.0.14 is a minor update to the Storybook's React renderer, building upon the functionality of the previous version, 7.0.13. Both versions share the same core set of dependencies, including essential tools like acorn for parsing, lodash for utility functions, and react-element-to-jsx-string for JSX conversion. The peer dependencies for React and React DOM remain consistent, ensuring compatibility with React versions 16.8.0, 17.0.0, and 18.0.0.
The key distinction between the two versions lies in the updated internal dependencies within the Storybook ecosystem. Specifically, @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.13 to 7.0.14. These updates likely incorporate bug fixes, performance improvements, or new features within those specific Storybook modules. While the core API and functionalities for rendering React components in Storybook remain largely the same between versions 7.0.13 and 7.0.14, upgrading to the latter ensures developers are utilizing the most recent and refined versions of Storybook's internal tooling. Developers can expect a seamless transition when updating to the latest version, ensuring their Storybook environment benefits from the newest enhancements in stability and functionality without major breaking changes. The only difference between the 2 releases is releaseDate as well.
All the vulnerabilities related to the version 7.0.14 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.