@storybook/addon-essentials package offers a suite of pre-configured Storybook addons designed to enhance the development and testing workflow. Version 7.0.21 builds upon the foundation established in version 7.0.20, delivering incremental improvements and bug fixes. A primary difference lies in the updated dependencies. While both versions share the same core set of addons like Actions, Measure, Outline, Controls, Toolbars, Viewport, Highlight, and Backgrounds, each addon is bumped to version 7.0.21 in the newer release to keep consistency, ensuring they work seamlessly together within the Storybook environment.
Developers leveraging @storybook/addon-essentials benefit from streamlined setup and convenient access to essential tools for visual testing, interaction recording, UI customization, and accessibility checks out of the box. The peer dependencies for React and React DOM remain consistent across both versions, ensuring compatibility with a wide range of React projects using versions 16.8.0 or higher. The file count and unpacked size experienced a slight increase from the older version, which is suggestive of minor code additions or adjustments. Version 7.0.21 was released on June 15, 2023, roughly a week after version 7.0.20, which came out on June 8, 2023. Staying updated to the latest version ensures access to the most refined and stable experience with these essential Storybook utilities.
All the vulnerabilities related to the version 7.0.21 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.