@storybook/addon-interactions enables developers to automate, test, and debug user interactions within Storybook stories, improving UI reliability and component behavior understanding. Version 7.0.7, released on April 24, 2023, follows closely on the heels of version 7.0.6, released on April 18, 2023. While both versions share the same core functionality and most dependencies, subtle but crucial differences exist. Examining the dependencies, the primary version bumps come within Storybook's internal packages ensuring consistent internal functionality. For example, @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger all move from version 7.0.6 to 7.0.7. These updates within the Storybook ecosystem likely contain bug fixes, performance improvements, and internal refinements that contribute to a more stable and streamlined experience when using the addon. From a developer's perspective, these incremental upgrades ensure access to the latest enhancements and resolutions within the broader Storybook environment. Developers can expect a seamless transition between versions since the core API and peer dependencies remain consistent. The package size and file count also remain consistent, indicating a focus on internal optimizations rather than significant feature additions between these specific releases. Upgrading to version 7.0.7 provides access to latest patches.
All the vulnerabilities related to the version 7.0.7 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.