@storybook/addon-interactions version 7.3.1 is a minor release over 7.3.0, focused on refinements and bug fixes rather than introducing major new features for automating, testing, and debugging user interactions in Storybook. Both versions share the same core functionality, allowing developers to create interactive stories and test user flows directly within the Storybook environment. Key dependencies like polished, jest-mock, and ts-dedent remain consistent, ensuring compatibility and predictable behavior. Importantly, the core Storybook dependencies such as @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger are all aligned with their respective Storybook versions (7.3.1 and 7.3.0), ensuring tight integration.
Developers utilizing @storybook/addon-interactions can leverage its features to build robust and testable components. The upgrade from 7.3.0 to 7.3.1 likely includes internal improvements and resolutions to reported issues improving stability and user experience. While the unpacked size and file count in the distributed package remained the same, the release date for version 7.3.1 is slightly later, suggesting a quick follow-up to address immediate concerns or minor adjustments. Both versions maintain the same peer dependencies for React and React DOM, reinforcing compatibility with a wide range of React projects. By consistently refining the addon, the Storybook team delivers a reliable tool for comprehensive interaction testing, thus solidifying its position as a vital asset in the component development workflow. Therefore upgrading is recommended.
All the vulnerabilities related to the version 7.3.1 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.