@storybook/addon-essentials is a vital package for Storybook users, bundling curated addons designed to enhance the Storybook experience and provide a comprehensive set of tools for component development and testing. Comparing versions 7.0.9 and 7.0.10, the core functionality remains consistent, but the newer version brings subtle improvements and bug fixes beneficial for developers.
Both versions include essential addons like @storybook/addon-docs for documenting stories, @storybook/addon-controls for live editing props, and various addons for actions, measuring, outlining, toolbars, viewport adjustments, highlighting, and background customization. Developers leverage these addons to create interactive and visually rich component showcases. The dependencies on libraries like ts-dedent, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, and @storybook/preview-api underpin the core functionality of the package. Both also share the same peer dependencies for React and React DOM, ensuring compatibility with a wide range of React projects.
The key difference lies in the resolved dependencies on other Storybook packages from 7.0.9 to 7.0.10. This suggests that version 7.0.10 likely includes internal updates and bug fixes within those dependent addons, ensuring greater stability and potentially unlocking enhanced features or performance improvements for the encompassing essentials package. Developers upgrading benefit from a more polished and reliable experience, thanks to these incremental improvements. Importantly both versions use the same Typescript version ^4.9.3 and @storybook/vue version, demonstrating the consistent support for these crucial development libraries.
All the vulnerabilities related to the version 7.0.10 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.