@storybook/addon-essentials is a crucial package for Storybook, offering a curated set of add-ons designed to enhance the development and presentation of UI components. Comparing versions 7.0.19 and 7.0.20 reveals subtle but important refinements for Storybook users. Both versions provide a consistent core set of features, including tools for documentation (addon-docs), interaction testing (addon-actions), visual debugging (addon-measure, addon-outline, addon-highlight), UI controls (addon-controls, addon-toolbars, addon-viewport, addon-backgrounds), and core utilities. They maintain identical peer dependencies, ensuring compatibility with React versions 16.8.0, 17.0.0, and 18.0.0, as well as consistent support for TypeScript and Vue development environments.
The primary difference lies in the updated versions of the internal Storybook dependencies. Version 7.0.20 bumps the versions of its dependencies such as @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, @storybook/preview-api, and all the other @storybook/addon-* packages, bringing them all to version 7.0.20. While the unpacked and file count remain same is fair to assume that the update delivers bug fixes and under-the-hood functional improvements that are included in the updated dependencies, contributing to a more stable and performant Storybook experience. Developers should upgrade to version 7.0.20 to benefit from the latest enhancements and ensure compatibility across the Storybook ecosystem. The consistent file size suggests optimized delivery and installation, which can improve both developer experience and potentially reduce load times during development and deployment.
All the vulnerabilities related to the version 7.0.20 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.