@storybook/addon-essentials is a collection of curated addons designed to enhance the Storybook development experience. Version 8.1.10, released on June 17, 2024, builds upon the prior stable version 8.1.9, released on June 13, 2024, offering subtle improvements and refinements. Both versions provide developers with essential tools like Docs, Actions, Measure, Outline, Controls, Toolbars, Viewport, Highlight, and Backgrounds, fostering a more efficient and visually complete component development workflow. A key benefit for developers is the streamlined integration of these commonly used addons, reducing configuration overhead and accelerating project setup.
The core dependencies remain consistent between the two versions, ensuring stability and compatibility within the Storybook ecosystem. Both rely on ts-dedent and a suite of core Storybook components, including @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, @storybook/preview-api, and others, all versioned to match the respective essentials package. The development dependency on TypeScript ^5.3.2 is also maintained, reinforcing a commitment to type safety and modern JavaScript development practices.
While the visible feature set remains largely the same, developers upgrading to 8.1.10 benefit from under-the-hood optimizations and bug fixes contributing to a smoother Storybook experience. While file count remained consistent, there was a small change in unpacked size of 14 bytes, suggesting minor internal adjustments. Ultimately, choosing 8.1.10 ensures developers are leveraging the most up-to-date and refined version of these essential Storybook tools.
All the vulnerabilities related to the version 8.1.10 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.