@storybook/addon-essentials streamlines Storybook configuration by bundling essential addons, enhancing the development experience for UI component libraries. Version 8.1.9 expands upon the solid foundation of 8.1.8, offering developers an optimized workflow with minimal breaking changes. Both versions offer crucial tools like Docs for automated documentation, Actions for interactive event monitoring, Controls for live prop editing, and Viewport for responsive design testing. Additional features encompass accessibility checks using Outline, precise measurements with Measure, theming with Backgrounds, and code highlighting through Highlight. Toolbars provide convenient customization options.
A key improvement in 8.1.9 lies in the updated dependencies, specifically within the Storybook ecosystem. While the core functionality remains consistent, the underlying modules like @storybook/addon-docs, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, @storybook/preview-api, @storybook/addon-actions, @storybook/addon-measure, @storybook/addon-outline, @storybook/addon-controls, @storybook/addon-toolbars, @storybook/addon-viewport, @storybook/addon-highlight, and @storybook/addon-backgrounds are all bumped to version 8.1.9, ensuring compatibility, bug fixes, and potential performance improvements across the board. The ts-dedent and typescript dependencies remain unchanged. This incremental upgrade assures developers a more stable and polished experience leveraging the latest Storybook features, enhancing the overall productivity and quality of their component development process. Always consult the official Storybook changelog for exhaustive details regarding version-specific enhancements and bug fixes.
All the vulnerabilities related to the version 8.1.9 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.