@storybook/addon-essentials is a collection of pre-configured Storybook addons designed to enhance the developer experience and streamline the creation of high-quality UI components. Versions 8.0.1 and 8.0.2 share the same fundamental goal: to provide a curated set of tools for actions, docs, measure, outline, controls, toolbars, viewport, highlight, and backgrounds, all within Storybook.
The key difference between version 8.0.1 and the newer 8.0.2 lies in the updated dependencies. While both versions depend on the same core set of addons critical for UI development, such as @storybook/addon-docs for documentation and @storybook/addon-controls for interactive property modification, each of these now point to their respective 8.0.2 releases in the latest version. This means that version 8.0.2 likely includes bug fixes, performance improvements, or new features within those individual addons that are not present in version 8.0.1.
Developers upgrading to 8.0.2 can expect improvements across the board, particularly in the functionalities provided by the individual addons. The update contributes to an overall more robust and feature-rich Storybook environment. Both versions utilize ts-dedent and are licensed under MIT, showing continued commitment to open-source principles by the Storybook team. The upgrade is recommended to leverage the latest improvements from the addon ecosystem.
All the vulnerabilities related to the version 8.0.2 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.