Storybook's @storybook/addon-interactions package, designed to automate, test, and debug user interactions within Storybook stories, saw a new release with version 7.4.4, following closely on the heels of version 7.4.3. While both versions share a similar core functionality and dependency structure, including dependencies like polished, jest-mock, and various Storybook core packages, the key distinction lies in the incremented version numbers for @storybook/* dependencies, bumped from 7.4.3 to 7.4.4 in the newer version. This synchronization across the Storybook ecosystem ensures compatibility and access to the latest features and bug fixes within the core framework.
Although the devDependencies like formik, typescript, @types/node, @storybook/jest, @storybook/testing-library and @devtools-ds/object-inspector and peerDependencies specifying React and React DOM versions remain consistent between releases, developers upgrading to 7.4.4 can expect subtle improvements and refinements inherited from the updated Storybook core packages. These updates typically address performance bottlenecks, enhance stability, or introduce minor API enhancements that improve the overall development experience. The release date also signifies a very recent update showing active maintainance of the package. For developers already using @storybook/addon-interactions, upgrading to 7.4.4 is highly recommended to benefit from the latest enhancements and ensure optimal compatibility within their Storybook environment.
All the vulnerabilities related to the version 7.4.4 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.