@storybook/addon-essentials provides a suite of essential add-ons that enhance your Storybook development experience. Version 7.0.14 builds upon the foundation of 7.0.13, offering subtle but important improvements. Both versions deliver core functionalities like Docs for automated documentation, Actions for interactive event logging, Controls for live prop editing, and Viewport/Backgrounds/Toolbars for customizing the Storybook preview. They share the same peer dependencies for React and React DOM, ensuring compatibility with a wide range of React projects (v16.8.0 and up).
The primary difference lies within the internal dependency versions of Storybook's own packages. Version 7.0.14 upgrades dependencies such as @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 all to version 7.0.14. This indicates a synchronized release, suggesting bug fixes, performance improvements, or new features across the Storybook ecosystem. For developers, upgrading to 7.0.14 is recommended to benefit from the latest refinements and ensure a consistent experience with other Storybook packages. Both versions use same dev dependencies. Consider that the unpacked size and file count are basically the same suggesting that the upgrades are focused on internal package dependecies improvements or fixes.
All the vulnerabilities related to the version 7.0.14 of the package
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.