@storybook/addon-essentials version 8.0.3 arrives as a subtle but important iteration over the previous 8.0.2, continuing to provide a curated set of Storybook addons designed to enhance the development and presentation of UI components. Both versions maintain the same core description emphasizing their role in unlocking the full potential of Storybook. From a developer's perspective, the key takeaway is the assurance of ongoing refinement within this essential addon package.
A primary difference lies in the version bump of the internal dependencies. Version 8.0.3 updates all @storybook/* dependencies, such as @storybook/addon-docs, @storybook/core-common, and @storybook/manager-api, @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 the changelog doesn't provide granular details, developers can anticipate bug fixes, performance improvements, and potentially new features within these underlying Storybook components reflected in version 8.0.3. If you were experiencing any minor glitches or seeking even better performance in areas covered by these addons, upgrading to 8.0.3 is recommended. Both versions share the same dev dependency (typescript) and metadata like license info and repository. More information about the specific updates can be found in the changelogs of the individual updated packages which is usually available on the github repository if the library. The release date difference (March 21st and March 19th respectively) suggests actively development is undergoing.
All the vulnerabilities related to the version 8.0.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.