The @storybook/addon-essentials package provides a suite of commonly used Storybook addons designed to enhance the development and documentation experience. Version 8.1.0, released on May 14, 2024, builds upon the previous stable version 8.0.10, released on May 5, 2024, by incrementing the core dependencies to their respective 8.1.0 versions including "@storybook/addon-docs", "@storybook/core-common", "@storybook/manager-api", "@storybook/node-logger", "@storybook/preview-api", and various other addons like "@storybook/addon-actions", "@storybook/addon-measure", and "@storybook/addon-controls". This synchronization ensures compatibility and access to the latest features and bug fixes offered by these individual addons. Developers upgrading to 8.1.0 can expect a more cohesive and up-to-date Storybook environment benefitting from improvements across the entire essentials package.
Furthermore, there are differences in the package metadata, notably in the "dist" section indicating changes in the packaged content. Version 8.1.0 exhibits "fileCount":33 and "unpackedSize":12684, compared to version 8.0.10's "fileCount":19 and "unpackedSize":9111, suggesting structural or content modifications impacting the overall size and file composition. While both versions use the same Typescript version, MIT license, and repository, this size difference means that developers migrating to version 8.1.0 might encounter slightly different performance or loading times compared to the prior version.
All the vulnerabilities related to the version 8.1.0 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.