@storybook/addon-essentials provides a suite of essential Storybook addons designed to enhance the development and testing workflow for UI components. Comparing versions 7.6.1 and 7.6.2, the primary difference lies in the synchronized updates of its core dependencies. Version 7.6.2 bumps every internal dependency, such as @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/preview-api, and other related addons like @storybook/addon-actions, @storybook/addon-controls, and @storybook/addon-viewport, to version 7.6.2 as well. This coordinated update suggests a focus on internal consistency and potential bug fixes or feature enhancements within the Storybook ecosystem.
For developers, this means upgrading to version 7.6.2 ensures they are leveraging the latest improvements and bug fixes across all the essential addons, promoting a more stable and feature-rich Storybook experience. While the dependencies update seems the most significant change between the versions, both versions maintain compatibility with React versions 16.8.0 through 18.0.0 and rely on the same ts-dedent and typescript peer and dev dependencies, respectively. Developers benefit from a consistent set of tools, like Actions, Controls, Docs, Viewport, Backgrounds, Highlight, Measure and Outline addons, that aids in component documentation, interaction testing, visual debugging, and responsive design testing directly within the environment. The update to 7.6.2 is most likely to bring minor improvements and fixes across the addons in essentials.
All the vulnerabilities related to the version 7.6.2 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.