@storybook/addon-interactions versions 7.0.15 and 7.0.14 are incremental releases focused on enhancing the debugging and testing experience for user interactions within Storybook. Both versions offer the core functionality of automating, testing, and debugging interactions in your stories, leveraging tools like jest-mock and ts-dedent. They also share a common set of dependencies including Storybook's core modules (@storybook/types, @storybook/global, @storybook/theming, etc.) and development dependencies like formik, typescript, and testing utilities from Storybook itself (@storybook/jest, @storybook/testing-library). Crucially, both versions maintain the same peer dependency requirements for React and ReactDOM, ensuring compatibility with versions 16.8.0, 17.0.0, and 18.0.0.
The primary distinction between the two versions lies in their release date and potentially very minor bug fixes or internal improvements. Version 7.0.15 was released later on May 23, 2023, suggesting it might include resolutions for issues discovered in version 7.0.14. For developers, it's generally recommended to use the latest stable version (7.0.15 in this case) to benefit from the most up-to-date bug fixes and potential enhancements, even if the changelog doesn't highlight significant functional changes. The distributed package size and file count remain consistent, so the update would likely be seamless. Always consult the official Storybook changelog for granular details on each release.
All the vulnerabilities related to the version 7.0.15 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.