@storybook/addon-essentials is a curated set of Storybook addons designed to enhance the developer experience and streamline the process of building, testing, and showcasing UI components. Comparing versions 7.0.16 and 7.0.17, the core functionality remains consistent, focusing on providing essential tools for Storybook users. Notably, both versions include vital addons such as @storybook/addon-docs for automated documentation, @storybook/addon-controls for interactive component controls, and various other addons like actions, measure, outline, toolbars, viewport, highlight, and backgrounds to facilitate comprehensive component testing and customization.
The primary difference between the two versions lies in the internal dependencies. Version 7.0.17 updates the internal dependencies of several addons, aligning them with the core Storybook version also at 7.0.17. This includes dependencies like @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, @storybook/preview-api, and others. These updates likely address bug fixes, performance improvements, or compatibility enhancements within the Storybook ecosystem. For developers, upgrading to version 7.0.17 ensures they're using the most recent and potentially most stable versions of these essential addons, guaranteeing better synergy across the Storybook environment and improved overall development workflow. Both versions maintain identical peer dependencies for React and React DOM, signifying no breaking changes in terms of React version compatibility and TypeScript and Vue version compatibility.
All the vulnerabilities related to the version 7.0.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.