@storybook/addon-interactions, a vital tool for automating, testing, and debugging user interactions within Storybook, saw a release of version 7.3.0 following closely after version 7.2.3. Both versions maintain the core functionality of the addon, empowering developers to create robust and reliable UI components. Examining the package data reveals key updates primarily centered around version alignment within the Storybook ecosystem.
A significant difference lies in the dependencies. Version 7.3.0 has updated its internal dependencies to align with the broader Storybook 7.3.0 release. This includes updates to @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger. Version 7.2.3 used the 7.2.3 tag for those dependencies. These updates likely incorporate bug fixes, performance improvements, and new features introduced in those core Storybook packages. Users upgrading to 7.3.0 will benefit from these enhancements, ensuring a more consistent and feature-rich Storybook experience.
The dist section also shows a minor change in unpackedSize, increasing from 142542 in 7.2.3 to 142686 in 7.3.0. This indicates that some code was added or modified to a certain extent. The release dates also show a small gap of 4 days, with version 7.3.0 releasing later.
For developers, upgrading to 7.3.0 is recommendend to benefit from the latest bug fixes and improvements that comes by using the newest dependencies for Storybook.
All the vulnerabilities related to the version 7.3.0 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.