@storybook/react version 7.4.5 is a minor release over 7.4.4, primarily focusing on internal dependency updates and refinements. While the core functionalities remain consistent, developers upgrading should note slight version bumps in Storybook's internal packages. Most notably, dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been updated from version 7.4.4 to 7.4.5. These internal updates usually bring bug fixes, performance improvements and enhanced stability within the Storybook ecosystem.
React, React-DOM and Typescript, remain peer dependencies, ensuring compatibility with existing React projects leveraging versions 16.8.0, 17.0.0 or 18.0.0. Developers can continue using their preferred React version without compatibility concerns. The development dependencies, including @babel/core, expect-type, require-from-string, @types/util-deprecate and jest-specific-snapshot remain unchanged, indicating a focus on the internal tooling used for developing and testing Storybook itself.
The absence of significant feature additions suggests that version 7.4.5 offers a stable and incremental improvement over version 7.4.4. Upgrading is encouraged to benefit from the latest bug fixes and stability enhancements within the Storybook renderer without introducing breaking changes. Both versions keep same dependencies like acorn, lodash, escodegen, html-tags, ts-dedent and others at same versions.
All the vulnerabilities related to the version 7.4.5 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.