@storybook/addon-essentials provides a curated set of essential Storybook addons designed to enhance the development and presentation of UI components. Comparing versions 8.0.4 and 8.0.3, the core difference lies in the synchronized versions of their dependent addons. Version 8.0.4 updates all its addon dependencies, such as @storybook/addon-docs, @storybook/addon-actions, @storybook/addon-controls, and others, to version 8.0.4, maintaining consistency across the Storybook ecosystem.
For developers, this means that upgrading to @storybook/addon-essentials@8.0.4 ensures compatibility and potentially unlocks new features or bug fixes present within the updated individual addons. This upgrade streamlines the Storybook experience, ensuring all essential utilities work harmoniously. While the core functionality of providing a suite of handy addons remains the same, staying up-to-date guarantees access to the latest improvements in areas like documentation generation with addon-docs, interactive controls with addon-controls, and visual debugging tools like addon-outline and addon-measure. Choosing the latest version signifies a commitment to a more reliable and feature-rich Storybook environment, benefiting both component creation and its collaborative presentation. The release date difference indicates quick maintenance, ensuring high quality for storybook users.
All the vulnerabilities related to the version 8.0.4 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.