@storybook/addon-interactions versions 7.0.3 and 7.0.2 both serve the purpose of automating, testing and debugging user interactions within Storybook. While the core functionality remains consistent, notable differences exist in their internal dependencies and release timing.
The 7.0.3 version signifies a more recent release, published on April 12, 2023, compared to version 7.0.2, which was released on April 3, 2023. This indicates that version 7.0.3 incorporates the latest bug fixes, performance enhancements, or dependency updates within the Storybook ecosystem. Reviewing the Storybook changelog for this specific patch version is recommended for a detailed understanding of included improvements.
The key distinction lies in the dependencies section, where all "@storybook/*" packages are upgraded from version 7.0.2 to 7.0.3. These updated dependencies encompass core components 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. This synchronized update ensures compatibility and takes advantage of the newest features and fixes within the encompassing Storybook framework.
For developers, this means upgrading to version 7.0.3 offers the advantage of a more refined and stable experience, ensuring alignment with the broader Storybook ecosystem. While both versions empower user interaction testing, the updated dependencies in version 7.0.3 provide access to the latest improvements, contributing to a more robust and feature-rich development workflow.
All the vulnerabilities related to the version 7.0.3 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.