@storybook/addon-interactions version 7.0.27 is a minor release over 7.0.26, primarily focusing on internal updates and dependency alignment within the Storybook ecosystem. Both versions are designed to automate, test, and debug user interactions within your Storybook stories, making it easier to ensure the quality and reliability of your UI components.
The core functionality remains consistent between the two versions. Developers can continue to leverage the addon's capabilities to create interactive stories, write tests directly within the Storybook environment, and debug user flows with ease. Existing interaction tests and debugging workflows should function seamlessly after upgrading.
Key dependencies like polished, jest-mock, and ts-dedent remain at the same versions, ensuring consistent behavior. The peer dependencies on react and react-dom also remain unchanged, supporting versions 16.8.0, 17.0.0, and 18.0.0.
The main difference lies in the aligned versions of Storybook's internal packages. Version 7.0.27 updates dependencies 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 to version 7.0.27. This ensures these parts of Storybook are working together as expected and that the addon benefits from any bug fixes or performance improvements introduced in the newer versions of these packages.
Developers should upgrade to version 7.0.27 to benefit from the latest internal improvements and ensure compatibility across the Storybook ecosystem. The update is expected to be seamless for most users, with no breaking changes anticipated in interaction testing or debugging capabilities.
All the vulnerabilities related to the version 7.0.27 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.