@storybook/addon-essentials is a collection of essential Storybook addons designed to enhance the development and testing workflow of UI components. Version 7.6.0 brings several updates compared to the previous stable version, 7.5.3. The primary difference lies in the synchronized core package versions. All @storybook/* dependencies within addon-essentials are updated to version 7.6.0, ensuring compatibility and access to the latest features and bug fixes across the Storybook ecosystem. This includes crucial packages like @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, and @storybook/preview-api, along with other addon utilities like @storybook/addon-actions, @storybook/addon-controls, and @storybook/addon-viewport. Developers upgrading to 7.6.0 can expect improved stability, performance enhancements, and any new functionalities introduced in these core dependencies. The dist information also shows a considerable difference in the fileCount and unpackedSize, with version 7.6.0 having a smaller footprint, potentially indicating optimized packaging or removal of redundant files. Both versions maintain the same peer dependencies for react and react-dom, ensuring compatibility with a wide range of React projects. This addon provides instant support for component documentation, interaction testing, visual tweaks via controls, and accessibility checks so developers can focus on building high quality components.
All the vulnerabilities related to the version 7.6.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.