@storybook/react version 7.0.0 represents a significant update to the popular UI component development tool compared to its previous stable version, 6.5.16. The most evident shift is in the dependency structure, with version 7.0.0 appearing to embrace a more modular architecture. Noticeably, a lot of @storybook/* dependencies are updated to version 7.0.0, aligning with the core Storybook release. Older version depends on webpack 4 while the new one does not specify the version.
Developers will appreciate the modernization in v7, including updated dependencies like type-fest and the removal of some older dependencies, potentially leading to a leaner bundle size. The shift away from some dependencies in v6.5.16 may also indicate improvements in the internal architecture, possibly simplifying the codebase and improving maintainability.
However, some utilities are not present in the new version, so you would need to evaluate if it is a breaking change for you.
The peer dependency requirements for React and React DOM remain consistent across both versions, ensuring compatibility with a wide range of React versions.
In essence, version 7.0.0 seems to be a refined and streamlined release, focusing on core Storybook functionalities and compatibility while potentially shedding older dependencies. Developers should evaluate their current usage of Storybook and test the upgrade to ensure a smooth transition, paying close attention to any impact from removed or updated dependencies.
All the vulnerabilities related to the version 7.0.0 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.