Storybook React has released version 7.5.2, a minor update following 7.5.1. Both are described as "Storybook React renderer" and share a common base, including core dependencies like React, React-DOM, and TypeScript. The minimal differences between them mainly include version upgrades in the internal Storybook packages. For example, @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, and @storybook/client-logger, @storybook/react-dom-shim dependencies have been updated from version 7.5.1 to 7.5.2.
These patch version updates suggest that version 7.5.2 primarily contains bug fixes and internal improvements rather than significant new features or breaking changes, therefore upgrading from 7.5.1 to 7.5.2 should be smooth.
Developers utilizing Storybook for React can expect continued stability and reliability in their component development workflow. Both versions maintain compatibility with React versions 16.8.0 and above, including versions 17 and 18. TypeScript users are also supported. It's crucial to examine the changelogs associated with the updated internal @storybook/* packages to understand the specific bug fixes and improvements included in the 7.5.2 release.
All the vulnerabilities related to the version 7.5.2 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.