@storybook/react versions 7.4.6 and 7.4.5 are incremental releases of the popular Storybook renderer for React applications. While both versions share the same core dependencies like acorn, lodash, react, and react-dom, there are subtle but important distinctions for developers to consider. A primary difference lies in the versions of Storybook's internal packages. Version 7.4.6 updates the internal dependencies @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim all to version 7.4.6, ensuring internal consistency and potentially including bug fixes or performance improvements within the Storybook ecosystem itself. These updates are integral for a smoother Storybook experience, particularly when leveraging newer features or addressing reported issues. Both versions support React versions ^16.8.0, ^17.0.0, and ^18.0.0, offering flexibility for projects using various React versions.The peer dependency on "typescript": "*" highlights that the library is designed to work with any version of Typescript, offering great flexibility when integrating the library in different projects. Finally, it's worth noting the release dates. Version 7.4.6 was released on October 3, 2023, after version 7.4.5 on September 24, 2023, reflecting ongoing development and maintenance efforts within the Storybook project. When upgrading, it is worth to check also the changelog to understand if there are specific fixes or features that can be beneficial for a specific use case in the new release.
All the vulnerabilities related to the version 7.4.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.