@storybook/addon-interactions versions 7.0.19 and 7.0.18 offer developers tools to automate, test, and debug user interactions within their Storybook stories. Both versions share the same core functionality, dependencies, and development tools, ensuring a consistent experience for users. Key dependencies like polished for styling, jest-mock for mocking, and ts-dedent for template literals remain consistent, as do peer dependencies for react and react-dom, guaranteeing compatibility with a wide range of React projects. Development dependencies like formik, @storybook/jest, and @storybook/testing-library also stay the same, providing robust testing capabilities during development.
However, a crucial distinction lies in the @storybook package versions. Version 7.0.19 of @storybook/addon-interactions aligns its internal 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, with its own version number (7.0.19). In contrast, version 7.0.18 utilized version 7.0.18 for these dependencies. This synchronization likely brings bug fixes, performance improvements, and new features from the core Storybook ecosystem to the interactions addon. Furthermore,version 7.0.19 was released on the 8th of June of 2023, almost 2 weeks after the version 7.0.18. Developers are encouraged to upgrade to version 7.0.19 for the latest enhancements and a more cohesive Storybook experience, ensuring they benefit from the most up-to-date functionalities within the Storybook environment.
All the vulnerabilities related to the version 7.0.19 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.