Version 7.4.1 of @storybook/addon-interactions represents a minor update over the previous stable version, 7.4.0, primarily focusing on refinements and internal improvements. Both versions cater to developers seeking to automate, test, and debug user interactions within their Storybook stories, ensuring a robust and reliable component development workflow. The core functionality remains consistent, leveraging dependencies like polished for styling, jest-mock for mocking, and @storybook/* packages for seamless integration with the wider Storybook ecosystem. Crucially, user-facing features related to interaction testing and debugging remain largely unchanged between the two versions.
Developers relying heavily on features like interaction recording, assertion generation, and visual debugging will experience a similar workflow in both versions. However, users should upgrade to 7.4.1 to benefit from any bug fixes or performance enhancements incorporated since the 7.4.0 release. The shared peer dependencies highlight compatibility with React versions 16.8.0 through 18.0.0, ensuring a broad range of React projects can readily adopt either version. While both versions list the same set of devDependencies, including @storybook/jest and @storybook/testing-library, indicating the intended testing ecosystem, developers should always consult the official Storybook changelog for detailed information on specific fixes or enhancements included in the 7.4.1 release. The consistent file count and unpacked size suggest minimal code changes between versions, reinforcing the impression of a maintenance release.
All the vulnerabilities related to the version 7.4.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.