@storybook/addon-interactions version 7.0.4 is a patch release over the previous version 7.0.3, both designed to automate, test, and debug user interactions within Storybook stories. The primary difference lies in the internal dependency versions of other core Storybook packages. Version 7.0.4 updates dependencies like @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger to their respective 7.0.4 counterparts. In contrast, version 7.0.3 uses the 7.0.3 versions of these dependencies.
For developers employing @storybook/addon-interactions, these changes likely represent bug fixes, performance improvements, or minor feature enhancements within the broader Storybook ecosystem, rather than dramatic alterations directly within the addon itself. The addon continues to rely on a robust set of packages like polished for styling, jest-mock for testing utilities, and ts-dedent for cleaner code.
Both versions maintain compatibility with React versions 16.8.0, 17.0.0, and 18.0.0 and use the same development dependencies. Upgrading from 7.0.3 to 7.0.4 is likely a straightforward process, intended to keep your Storybook environment aligned with the latest improvements and fixes across the Storybook platform.
All the vulnerabilities related to the version 7.0.4 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.