@storybook/addon-interactions is a vital tool for Storybook users, enabling automation, testing, and debugging of UI interactions within their components. Version 7.0.25 builds upon the solid foundation of 7.0.24, offering the same core benefits of streamlined interaction testing and enhanced debugging capabilities. Developers can leverage this addon to create robust and reliable user interfaces by simulating user behaviors directly within their Storybook environment. This eliminates the need for external testing frameworks for basic interaction validation, leading to faster development cycles.
While the core functionality remains consistent between versions 7.0.24 and 7.0.25, the key difference resides in the internal dependency versions, specifically within the Storybook ecosystem itself. Version 7.0.25 upgrades its dependencies to align with the broader Storybook framework (e.g., @storybook/types, @storybook/theming, @storybook/components, etc). These updates, though not directly reflected in new features, ensure compatibility and stability within the Storybook environment. For developers, upgrading to 7.0.25 is recommended to maintain a cohesive and up-to-date Storybook setup, reducing the risk of potential conflicts or unexpected behaviors arising from mismatched dependency versions. The upgrade ensures you're leveraging the latest improvements and bug fixes across the Storybook platform. The underlying peer dependencies remain the same (React and React DOM versions), meaning the upgrade process remains smooth for most users.
All the vulnerabilities related to the version 7.0.25 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.