@storybook/addon-essentials is a crucial package for Storybook users, bundling a collection of essential add-ons designed to enhance the development and testing workflow. Version 8.0.10 builds upon the solid foundation of 8.0.9, offering subtle improvements and refinements that contribute to a more seamless Storybook experience.
The primary difference between the versions lies in the updated dependency versions. Version 8.0.10 depends on the 8.0.10 versions of @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, while version 8.0.9 depends on the 8.0.9 versions of those same packages. This ensures that all the core Storybook components within the essentials package are synchronized and compatible, which is important for avoiding potential conflicts or unexpected behaviors. The change in unpackedSize from 9097 to 9111 suggests minor augmentations and fixes within those underlying dependencies, adding to the overall optimization of the included features.
While the developer experience remains largely consistent between the two versions, it is still worthwhile upgrading, which would update all the sub dependencies as well, to leverage the latest bug fixes, performance improvements, and potentially new features introduced within those individual add-ons. Developers benefit from features like live editing with controls, interactive documentation using @storybook/addon-docs, visual testing with @storybook/addon-viewport and @storybook/addon-backgrounds, accessibility checks, and actions logging. With the upgrades, developers can ensure they're working with the most stable and feature-rich environment for building and showcasing UI components within Storybook. Version 8.0.10, although appearing incrementally different is the better updated version to work on.
All the vulnerabilities related to the version 8.0.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.