@storybook/addon-interactions, a tool designed to automate, test, and debug user interactions within Storybook, saw a minor version update from 7.0.1 to 7.0.2 on April 3rd, 2023. While the core functionality remains consistent, examining the dependencies reveals where the changes lie. Both versions share the same development dependencies, including formik, typescript, @types/node, @storybook/jest, @storybook/testing-library, and @devtools-ds/object-inspector, suggesting no changes in the packages used for internal development processes or testing.
Similarly, the peer dependencies for React and ReactDOM remain the same, indicating compatibility is maintained across React versions 16.8.0, 17.0.0, and 18.0.0. The descriptions, license, repository information, funding details, and file counts are also identical.
The key difference between version 7.0.1 and 7.0.2 lies in the individual versions of the dependencies this addon relies on - all dependencies are upgraded to version 7.0.2 (were at 7.0.1). This suggests that the update primarily addresses internal compatibility issues or bug fixes within the Storybook ecosystem itself. Developers already using version 7.0.1 should consider upgrading to ensure they are leveraging the latest improvements of the Storybook core, especially if experiencing any compatibility problems. The addon continues to provide a powerful way to create robust and interactive stories.
All the vulnerabilities related to the version 7.0.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.