Storybook React has released a new version, 7.6.16, following closely on the heels of 7.6.15. While the core functionality remains consistent as a powerful tool for building UI components in isolation within React projects, a closer look reveals subtle yet important changes for developers to consider. The primary distinction between the two versions lies in dependency updates, specifically within Storybook's internal packages. Version 7.6.16 updates @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger and @storybook/react-dom-shim to version 7.6.16, indicating internal improvements and bug fixes within these core modules. Developers can expect refinements in the documentation generation, core client interactions (likely affecting addon functionalities and communication with the Storybook server), the preview API (impacting how stories are rendered and interact), client-side logging, and the React DOM shim ensuring compatibility. These updates likely address underlying issues and edge cases discovered in the previous version, enhancing the stability and reliability of the Storybook environment. The peer dependencies, build tools, and other core dependencies remain largely the same, so the migration should be smooth. Carefully check the changelog for a detailed explanation of what was fixed or improved inside the updated @storybook/* packages to decide if you should update.
All the vulnerabilities related to the version 7.6.16 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.