@storybook/addon-interactions, a vital tool for automating, testing, and debugging user interactions within Storybook, saw a recent update from version 7.0.11 to 7.0.12. While seemingly a minor version bump, these changes can impact developers leveraging this addon. The core functionality remains consistent, enabling robust interaction testing through features like automated assertions and visual debugging. Both versions share the same set of development dependencies, including testing utilities like @storybook/jest and @storybook/testing-library, alongside typing support from typescript and @types/node. Peer dependencies for react and react-dom also remain unchanged, ensuring compatibility with a broad range of React versions (16.8.0 to 18.0.0).
A key difference lies within the dependencies. Version 7.0.12 upgrades its internal @storybook/* package dependencies, aligning them to version 7.0.12. This update signals a synchronization with the broader Storybook ecosystem. While the specific changes within these internal packages aren't detailed here, developers should anticipate bug fixes, performance improvements, or new features within the Storybook core that indirectly benefit the addon's functionality. Users should review the release notes for Storybook 7.0.12 to understand the implications of these synchronized updates. The release date also gives insights with 7.0.12 being released on May 15, 2023, indicating an incremental update focusing on internal package alignment.
All the vulnerabilities related to the version 7.0.12 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.