@storybook/addon-interactions empowers developers to automate, test, and debug user interactions within Storybook stories, ensuring components behave as expected under various conditions. Version 7.0.0 represents a significant update compared to version 6.5.16, reflecting Storybook's evolution. A key difference lies in the dependency structure. Version 7.0.0 aligns with Storybook's modular architecture, directly depending on core packages like @storybook/types, @storybook/global, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger, all at version 7.0.0. This tight integration enables seamless compatibility and unlocks the latest features and improvements across the Storybook ecosystem.
In contrast, version 6.5.16 relied on older, specific versions of packages such as @storybook/api, @storybook/addons, and @storybook/csf. The newer version streamlines dependencies and removes some like core-js and global while adding @storybook/jest and @storybook/testing-library to dev dependencies, signaling a possible shift in testing approach or improved integration with these testing utilities compared to earlier versions. These changes aim to provide a modern, more stable, and feature-rich experience for developers creating interactive stories. Developers migrating to version 7.0.0 can expect enhanced performance, updated components, and improved alignment with the overall Storybook architecture. The reduction in fileCount and unpackedSize in version 7.0.0 could imply a more streamlined and optimized package distribution.
All the vulnerabilities related to the version 7.0.0 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.