@storybook/addon-interactions streamlines the process of automating, testing, and debugging user interactions within your Storybook stories, improving the reliability and maintainability of your UI components. Comparing versions 7.4.6 and 7.4.5, while seemingly incremental, reveals key updates relevant to developers.
The core functionality and dependency structure remain largely consistent, leveraging tools like polished for styling, jest-mock for mocking, and ts-dedent for cleaner template literals. Both versions share the same peer dependencies for react and react-dom, ensuring compatibility across different React versions (16.8.0, 17.0.0 and 18.0.0). Crucially, the direct dependencies on other @storybook/* packages are bumped to version 7.4.6 in the newer release, aligning it with the latest Storybook ecosystem. This subtle change signifies internal synchronization and potentially unlocks new features or bug fixes within the broader Storybook framework.
While the devDependencies remains identical, with packages like formik, typescript, @storybook/jest, @storybook/testing-library, and @devtools-ds/object-inspector aiding development and testing workflows, the primary benefit of upgrading to 7.4.6 lies in leveraging the latest and greatest from Storybook's core. Developers benefit from the most recent bug fixes, performance improvements, and potentially refined APIs within the @storybook/* dependencies. By updating, developers ensure they are building on the solid foundation providing the best experience for interaction testing within Storybook. The release date difference also highlights this upgrade brought potentially compatibility fixes improving your workflow.
All the vulnerabilities related to the version 7.4.6 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.