@storybook/addon-interactions, a vital tool for automating, testing, and debugging user interactions within Storybook, saw a refinement with version 7.0.18, released on May 26, 2023, following version 7.0.17 released on May 24, 2023. While the core functionality remains consistent, visible in the shared description, subtle yet potentially impactful changes occurred under the hood.
Examining the dependencies, version 7.0.18 shifts to depend on @storybook packages version 7.0.18 such as @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, and @storybook/instrumenter from version 7.0.17 to version 7.0.18, signifying a synchronization across the Storybook ecosystem. These synchronizations often include bug fixes, performance tweaks, and internal API adjustments that ensure seamless compatibility and enhance the overall developer experience. Developers should particularly take note of correlated updates to @storybook/manager-api and @storybook/preview-api, because these packages influence how interactions are defined and visualized within the Storybook UI.
The underlying framework dependencies like polished, jest-mock, and ts-dedent remain untouched, solidifying the core functionalities of the package. Importantly, peer dependencies for react and react-dom are consistent, ensuring continued support for a wide range of React versions. Developers utilizing @storybook/addon-interactions should thus update their Storybook installations to version 7.0.18 to harness the benefits of these synchronized improvements that maintain a robust and reliable workflow for UI testing and debugging. It is likely that this upgrade will make interaction testing run better and more efficiently.
All the vulnerabilities related to the version 7.0.18 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.