@storybook/addon-essentials versions 7.3.2 and 7.3.1 offer curated Storybook addons designed to enhance the development and presentation of UI components. Both versions provide a suite of essential tools, including @storybook/addon-docs for generating documentation, @storybook/addon-actions for logging interactions, @storybook/addon-controls for interactive prop modification, and various visual aid addons like @storybook/addon-measure, @storybook/addon-outline, @storybook/addon-backgrounds, @storybook/addon-viewport, and @storybook/addon-highlight. These tools streamline the development workflow, promote consistency and improve the overall Storybook experience.
The key change between versions 7.3.1 and 7.3.2 lies in the updated dependencies. All internal @storybook addons listed as dependencies were bumped from version 7.3.1 to 7.3.2. While the core functionality remains consistent, this dependency update likely includes bug fixes, performance improvements, and minor feature enhancements within those individual addons. For developers, upgrading to 7.3.2 ensures they are utilizing the most up-to-date and refined versions of these essential Storybook tools, potentially leading to a smoother and more efficient component development and testing process. React developers utilizing Storybook can safely upgrade, considering the peer dependency remains compatible with React versions 16.8.0 through 18.0.0. The upgrade to 7.3.2 represents a worthwhile step for maintaining a robust and feature-rich Storybook environment for UI development.
All the vulnerabilities related to the version 7.3.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.