@storybook/addon-interactions versions 7.3.2 and 7.3.1 offer developers tools to automate, test, and debug user interactions within Storybook stories. Both versions share a common foundation, relying on dependencies like polished for styling, jest-mock for mocking, and ts-dedent for template literals. They also include core Storybook modules. However, the key difference lies in the updated internal dependencies across the Storybook ecosystem. Version 7.3.2 pulls in the latest iterations of @storybook/types, @storybook/theming, @storybook/components, @storybook/core-common, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/instrumenter, and @storybook/client-logger, all incremented to version 7.3.2 to ensure internal consistenty between all the modules of the Storybook framework.
Developers leveraging @storybook/addon-interactions utilize its features to create stories that go beyond static presentations. The addonenables the recording and playback of user actions, allowing for automated testing of component behavior. Useful in creating robust and verifiable user flows directly within the Storybook environment. When upgrading to the latest version, 7.3.2, developers benefit from potential bug fixes, performance improvements, and new features introduced within the core Storybook modules, providing a smoother and more reliable experience when building, testing, and showcasing their UI components. The upgrade ensures the addon interfaces seamlessly with other Storybook components. While the core functionalities remain consistent, the updated dependencies can bring subtle but impactful enhancements optimizing the overall developer workflow.
All the vulnerabilities related to the version 7.3.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.