@storybook/addon-interactions version 7.2.2 introduces subtle but important updates for developers using Storybook to automate, test, and debug user interactions. While the core functionality remains consistent, this release signifies ongoing maintenance and refinement of the addon. Comparing it to the previous stable version, 7.2.1, the most apparent change lies in the updated dependencies on other Storybook packages. Key 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 have been bumped to version 7.2.2, aligning them with the latest Storybook ecosystem improvements.
For developers, this means access to bug fixes, performance improvements, and potentially new features incorporated within these core Storybook modules that directly benefit the interactions addon. Libraries such as polished, jest-mock and ts-dedent remain on the same version. By staying current with the Storybook ecosystem, version 7.2.2 ensures better compatibility and a more seamless development experience when building interactive stories. The other dependencies and peer dependencies remain the same. The updated release date also indicates recent activity and maintenance within the Storybook project.
All the vulnerabilities related to the version 7.2.2 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.