@storybook/addon-interactions is a powerful tool for automating, testing, and debugging user interactions within Storybook stories, facilitating robust UI development. Comparing versions 7.0.13 and 7.0.12, the core functionality remains consistent, focusing on providing developers with the ability to create interaction tests that simulate user behavior and verify the resulting state changes in their components. Both versions include dependencies like polished for styling utilities, jest-mock for mocking functionalities, and @storybook/* packages for seamless integration with the Storybook ecosystem.
The key difference lies in the version bumps of the internal Storybook dependencies. Version 7.0.13 upgrades 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 from 7.0.12 to 7.0.13. These updates typically incorporate bug fixes, performance improvements, and new features within the broader Storybook environment. Therefore, upgrading to 7.0.13 ensures developers benefit from the latest enhancements and stability improvements across the entire Storybook platform. The size of the packages is exactly the same and also the number of files included in the package. From a development perspective, sticking to the most recent version of the library provides the user with the guarantee that they are using the latest version of the tool and its dependencies, with the benefits that come with it.
All the vulnerabilities related to the version 7.0.13 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.