@storybook/addon-essentials is a curated set of Storybook addons designed to enhance the development experience. Version 7.4.5 introduces subtle improvements over the previous 7.4.4, primarily focusing on dependency updates across the Storybook ecosystem. Diving into the details, version 7.4.5 upgrades its internal dependencies such as @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, @storybook/preview-api, and a host of other addon dependencies like @storybook/addon-actions, @storybook/addon-measure etc. to the 7.4.5 versions.
While on the surface, these may appear as minor version bumps, they signify a commitment to maintaining consistency and compatibility within the Storybook environment. Developers benefit from these updates through improved stability, potential performance enhancements, and alignment with the latest features offered by individual addons. In essence, 7.4.5 ensures that the "essentials" work seamlessly together providing a smoother and more robust Storybook experience.
From a developer perspective, upgrading to 7.4.5 is generally recommended to leverage these incremental improvements. Though the core functionalities of the addon-essentials bundle remain consistent between 7.4.4 and 7.4.5, the underlying dependency updates solidify the foundations. Consider testing your Storybook setup after upgrading to confirm compatibility, especially if you heavily rely on specific features offered by any of the included addons.
All the vulnerabilities related to the version 7.4.5 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.