@storybook/addon-interactions, designed for automating, testing, and debugging user interactions within Storybook, saw a release of version 7.5.0 after version 7.4.6. Both versions maintain core dependencies like polished, jest-mock, and ts-dedent, ensuring consistent styling and testing capabilities. The key difference lies in the updated Storybook core packages, with version 7.5.0 depending on "@storybook/types": "7.5.0", "@storybook/theming": "7.5.0", "@storybook/components": "7.5.0", "@storybook/core-common": "7.5.0", "@storybook/core-events": "7.5.0", "@storybook/manager-api": "7.5.0", "@storybook/preview-api": "7.5.0", "@storybook/instrumenter": "7.5.0", "@storybook/client-logger": "7.5.0" while 7.4.6 relies on "7.4.6" versions of those packages. This ensures compatibility with the latest Storybook features and improvements.
For developers, upgrading to 7.5.0 means leveraging the newest enhancements in Storybook's core, potentially impacting how interactions are tested and debugged. While both versions share identical devDependencies such as formik, typescript, @storybook/jest, @storybook/testing-library, and @devtools-ds/object-inspector, the subtle difference in @types/node dependency, "^18.0.0" vs "^16.0.0", of the newest can indicate improved support for recent Node.js versions. Developers should particularly note the peer dependency requirements for React and React DOM remain consistent across both versions, ensuring broad compatibility across different project setups. The upgrade promises a smooth transition with enhanced stability and access to the latest Storybook functionalities related to user interaction testing, making it a worthwhile update for projects already utilizing Storybook.
All the vulnerabilities related to the version 7.5.0 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.