@storybook/addon-essentials is a collection of essential Storybook addons designed to enhance the development and testing workflow for UI components. Version 7.0.22 and 7.0.21 offer similar functionalities, providing developers with a curated set of tools to streamline their component development process. Both versions include vital addons like @storybook/addon-docs for generating documentation, @storybook/addon-actions for logging interactions, @storybook/addon-controls for live editing component props, and addons for visual enhancements such as @storybook/addon-measure, @storybook/addon-outline, @storybook/addon-backgrounds, and @storybook/addon-viewport. These addons facilitate ease of use and improves the visual representation and user experience for developers and stakeholders.
The key difference between version 7.0.21 and 7.0.22 lies in the minor version update, and the release date, indicating the fixes, stability and improvements. Developers leveraging Storybook in their React projects can benefit from both versions, as they are compatible with React versions 16.8.0 and later. The dependency versions of other @storybook packages have been bumped to match the main package version, thus ensuring that the entire framework operates cohesively. When upgrading from 7.0.21 to 7.0.22, developers should expect primarily bug fixes and incremental improvements, and are recommended to review the Storybook changelog for detailed information on any specific changes or new features.
All the vulnerabilities related to the version 7.0.22 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.