@storybook/addon-essentials is a collection of essential Storybook addons designed to enhance the development and debugging experience. Version 7.0.26, released on July 5th, 2023, follows closely on the heels of version 7.0.25, released just two days prior on July 3rd, 2023. A key difference between these versions lies in their internal dependency versions. While both share the same core description, dependencies, devDependencies including Typescript 4.9.3 and Vue integration via @storybook/vue, and peer dependencies requiring React and React DOM versions 16.8.0 or later, version 7.0.26 upgrades the versions of its internal Storybook addon dependencies. Specifically, addons like @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, and others are bumped from version 7.0.25 to 7.0.26 to ensure consistency and to include latest bug fixes and improvements.
For developers already using Storybook 7.0, this update provides a simple means to stay aligned with the latest refinements within their Storybook environment. The update signifies a commitment to providing reliable and stable tooling for UI development, enabling users to leverage components effectively.The fast pace of the releases confirms the project is actively maintained, with a dedication to solving and enhancing functionalities quickly. Given the minimal time between the releases, upgrading from 7.0.25 to 7.0.26 is advisable to take advantage of the newest refinements present across essential Storybook tools, like documentation features.
All the vulnerabilities related to the version 7.0.26 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.