@storybook/addon-interactions version 7.0.6 is a minor release following 7.0.5, designed to enhance the interaction testing and debugging experience within Storybook. Both versions provide tools for automating, testing, and debugging user interactions within your components but the later version integrates newer versions of Storybook internal dependencies improving the global user experience and stability. The core functionalities remain consistent: leveraging tools like jest-mock, @storybook/jest, and @storybook/testing-library for creating robust interaction tests within your stories. Developers will find the polished and ts-dedent dependencies useful for styling and maintainability. The library allows simulating user actions within stories, verifying expected component behavior, and visually debugging interaction flows directly in the Storybook UI. Crucially, both versions maintain compatibility with React versions 16.8.0, 17.0.0, and 18.0.0. The small change between versions means that most users can upgrade without any major breaking changes in their code and still get the lastest improvements and bug fixes. The update to version 7.0.6 ensures users benefit from the latest improvements, bug fixes, and dependency updates within the Storybook ecosystem, contributing to a more seamless and reliable development workflow.
All the vulnerabilities related to the version 7.0.6 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.