@storybook/addon-essentials version 8.0.6 is a minor update to the curated collection of Storybook addons designed to enhance the development and testing workflow for UI components. Comparing it to the previous stable version, 8.0.5, the core functionality remains consistent, focusing on providing essential tools to developers. Both versions include dependencies like @storybook/addon-docs for documentation generation, @storybook/addon-actions for tracking user interactions, @storybook/addon-controls for live editing component props, and other addons such as @storybook/addon-measure and @storybook/addon-outline for visual debugging of layouts. Addons for customizing the storybook's UI like @storybook/addon-toolbars, @storybook/addon-viewport, @storybook/addon-highlight and @storybook/addon-backgrounds remain unchanged.
The key difference lies in the bumped versions of the internal Storybook dependencies. Version 8.0.6 upgrades these dependencies (e.g., @storybook/addon-docs, @storybook/core-common, @storybook/manager-api) to their respective 8.0.6 releases. These updates often include bug fixes, performance improvements, and compatibility enhancements within the Storybook ecosystem. For developers, this means a potentially more stable and refined experience, especially if they encountered issues in the previous 8.0.5 release. The devDependencies and other metadata, such as licensing and repository information, remain consistent between the two versions, indicating a focused maintenance release. Upgrading to 8.0.6 is generally recommended to benefit from the latest improvements and ensure compatibility with the broader Storybook environment, offering a smoother and more efficient UI development process.
All the vulnerabilities related to the version 8.0.6 of the package
Cross site scripting in markdown-to-jsx
Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.
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.