@storybook/addon-interactions versions 7.0.8 and 7.0.7 offer tools for automating, testing, and debugging user interactions within Storybook. Both versions share a common foundation, relying on dependencies like polished for styling, jest-mock for mocking, and @storybook/* packages for core Storybook functionality. They also share development dependencies such as formik for form handling, typescript for type safety, and @storybook/jest and @storybook/testing-library for robust testing capabilities. React and React DOM are peer dependencies, ensuring compatibility with versions 16.8.0, 17.0.0, and 18.0.0.
The key difference lies in the bug fixes and internal improvements that come with the patch update. Developers upgrading to 7.0.8 can expect a more stable and refined experience. Version 7.0.8 utilizes newer versions of internal storybook dependencies, like @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter and @storybook/client-logger. In this version the unpacked size of the package in increased of about 700 bytes. While the differences are subtle, staying current helps leverage the latest enhancements, ultimately contributing to a smoother workflow for building and testing interactive components within Storybook. Upgrading ensures users benefit from the most recent refinements and bug fixes in interaction testing.
All the vulnerabilities related to the version 7.0.8 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.