@storybook/addon-essentials is a collection of curated addons designed to enhance the Storybook development experience. Version 8.1.3 builds upon the solid foundation of 8.1.2, offering developers a refined toolkit for building and showcasing UI components. Both versions include essential addons like @storybook/addon-docs for automated documentation, @storybook/addon-controls for interactive component customization, and @storybook/addon-actions for tracking user interactions. Further enhancing visual exploration are addons such as @storybook/addon-viewport, @storybook/addon-backgrounds, @storybook/addon-outline, @storybook/addon-measure and @storybook/addon-highlight, all of which remain consistent between the two versions at their respective version numbers. The dependencies like ts-dedent, @storybook/core-common, @storybook/manager-api, @storybook/node-logger and @storybook/preview-api are also kept consistent with their respective version numbers to ensure seamless functionality. While the core features remain largely the same, the upgrade from 8.1.2 to 8.1.3 ensures you're benefiting from the latest bug fixes and internal optimizations within the Storybook ecosystem. The release date difference of approximately two days indicates a focused effort on continuous improvement. The file count and the unpacked size of the library remain unchanged between versions, keeping the library lightweight.
All the vulnerabilities related to the version 8.1.3 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.