@storybook/addon-interactions is a vital Storybook addon designed to enhance the way developers automate, test, and debug user interactions within their components. Version 7.0.10 builds upon the robust foundation laid by version 7.0.9, offering subtle yet noteworthy improvements. A key difference lies in the updated dependencies, specifically within the core Storybook packages. Version 7.0.10 upgrades dependencies like @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, and @storybook/instrumenter, and @storybook/client-logger all to version 7.0.10. These upgrades ensure better compatibility, potentially introduce bug fixes, and provide the latest features from the core Storybook ecosystem to this addon.
While the developer dependencies and peer dependencies remain consistent between the two versions, this core update means developers adopting 7.0.10 benefit from the most recent advancements and stability improvements within the entire Storybook framework. Developers integrating or upgrading should be aware of these synchronized core package versions and check the Storybook changelog for details to ensure a smooth transition and fully leverage the enhanced interaction testing capabilities. It is important to notice the small size difference between the packages, due to the different versions of the dependencies. Also, the release date difference is important to notice, as the 7.0.10 version is more recent and stable.
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.