The @storybook/react package, a crucial renderer for building UI components in isolation within a Storybook environment, has been updated from version 7.6.16 to 7.6.17. While the core functionality remains consistent, developers should be aware of subtle yet important changes between these versions. Examining the dependencies reveals the most significant difference: internal Storybook packages have been bumped from version 7.6.16 to 7.6.17. These changes likely encompass bug fixes, performance improvements, or minor feature enhancements within the Storybook ecosystem.
For developers, this update signifies a commitment to stability and ongoing improvements within the Storybook platform. While a direct line-by-line comparison of code isn't available from this data alone, the consistent file count and the relatively small size of the package suggest no radical architectural shifts. Instead, developers using @storybook/react can expect a more refined and robust experience, benefiting from the collective fixes and enhancements made across the core Storybook modules.
The update ensures closer alignment and compatibility between rendering functionalities and core modules, thus preventing the rise of any incompatibility errors if other modules are also updated. Developers can confidently upgrade to version 7.6.17, knowing it incorporates the latest refinements while maintaining their existing React-based Storybook setups, while taking advantage of recent bug fixes and improvements.
All the vulnerabilities related to the version 7.6.17 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.