@storybook/addon-interactions, a vital tool for automating, testing, and debugging user interactions within Storybook, saw a recent update from version 7.0.13 to 7.0.14. While the core functionality remains consistent, several underlying dependencies have been bumped to their respective 7.0.14 versions to maintain cohesion with the broader Storybook ecosystem. Specifically, dependencies like @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 all been updated.
This update ensures compatibility and access to the latest features and bug fixes within these core Storybook modules. Developers leveraging @storybook/addon-interactions will benefit from enhanced stability and potentially improved performance derived from these dependency upgrades. The peer dependencies, react and react-dom remain the same, allowing a compatible usage with versions 16.8.0, 17, and 18.
For developers new to the addon, @storybook/addon-interactions empowers them to write automated tests that simulate user behavior within Storybook stories. It helps catch interaction-related bugs early in the development process, resulting in more robust and user-friendly components. By upgrading to the latest version, developers are ensuring they are using the most up-to-date and reliable version of the addon, optimized for seamless integration with the Storybook platform. The release date is also updated from May 22nd to May 23rd, so users can easily know which is the newest version.
All the vulnerabilities related to the version 7.0.14 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.