@storybook/addon-interactions saw a minor version bump from 7.0.4 to 7.0.5, primarily involving updates to internal Storybook packages. Examining the dependencies reveals that numerous core Storybook packages 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 were updated from version 7.0.4 to 7.0.5.
For developers using @storybook/addon-interactions, this update likely brings improvements and bug fixes inherited from those core Storybook updates. Whilst there appear to be no direct changes to the addon's code, the deep dependency on Storybook's core means the addon benefits from underlying platform improvements. This highlights the importance of staying up-to-date with the latest version to ensure compatibility and leverage the latest enhancements within the Storybook ecosystem.
The addon facilitates automating, testing, and debugging user interactions within Storybook stories, a vital part of modern component-driven development workflows. Therefore, keeping this addon aligned with the core Storybook version ensures a smoother and more reliable experience when building and maintaining interactive components which makes this update beneficial. Developers should be aware that whilst there aren't specific documented changes for the addon itself, implicit enhancements from the core library are part of the reason to update, alongside more broader gains.
All the vulnerabilities related to the version 7.0.5 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.