The @storybook/addon-essentials package, a curated collection of Storybook addons designed to enhance the development and viewing experience, saw a minor update from version 7.6.5 to 7.6.6 in December 2023. Both versions aim to bring the best out of Storybook with features like documentation generation, logging, interaction controls, and visual aids, streamlining the UI development workflow. A noteworthy difference lies in the release dates, with version 7.6.6 being published on December 19th, 2023, a few days after version 7.6.5 which was released on December 15th, 2023.
Looking at the dependencies, both versions depend on the same core Storybook addons and utilities like @storybook/addon-docs, @storybook/core-common, @storybook/manager-api and more including the versioning which is consistent across both versions, suggesting that the update might include bug fixes or minor enhancements within the essential addon package rather than major feature additions to those core dependencies. Developers using React or ReactDOM versions 16.8.0 or later, up to version 18, won't experience compatibility issues as indicated by the peer dependencies. Consequently, users can expect similar functionalities in both versions, but upgrading to 7.6.6 is generally recommended to benefit from the latest patches and improvements ensuring a more stable and refined Storybook experience. Both distributions have the same file count of 19 and unpacked size of 9375.
All the vulnerabilities related to the version 7.6.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.