@storybook/addon-interactions, a vital tool for automating, testing, and debugging user interactions within Storybook, has seen a recent update from version 7.4.1 to 7.4.2. While the core functionality remains consistent, indicated by the identical description, fileCount, and unpackedSize, developers should note the bumped version numbers across its internal dependencies. 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 been updated from 7.4.1 to 7.4.2 to align with the core Storybook ecosystem.
This update signifies that version 7.4.2 incorporates the latest refinements and bug fixes present in Storybook's underlying components. For developers utilizing this addon, upgrading ensures compatibility and leverages the improvements introduced in the broader Storybook platform. Although the changes might be subtle, they contribute to a more stable and performant development environment. Furthermore, the release date difference identifies that 7.4.2 was released approximately four days after 7.4.1. Always refer to the official Storybook changelog for detailed information on the specific changes included in version 7.4.2 to understand the full extent of the update and adapt their workflows accordingly.
All the vulnerabilities related to the version 7.4.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.