@storybook/addon-essentials is a crucial package for Storybook users, bundling together a set of add-ons designed to enhance the development and testing workflow. Comparing versions 7.0.7 and 7.0.6, the core functionality remains consistent, focusing on providing essential tools for UI development. Both versions include dependencies such as ts-dedent for template literal manipulation, @storybook/addon-docs for auto-generated documentation, @storybook/core-common, @storybook/manager-api, @storybook/node-logger, and @storybook/preview-api for internal Storybook workings. Crucially, a suite of user-facing add-ons is included: @storybook/addon-actions for logging interactions, @storybook/addon-measure and @storybook/addon-outline for visual debugging, @storybook/addon-controls for interactive prop editing, @storybook/addon-toolbars for UI customization, @storybook/addon-viewport for responsive design testing, @storybook/addon-highlight for code highlighting, and @storybook/addon-backgrounds for theming.
The key difference lies in the version bump of the included dependencies. Version 7.0.7 updates dependencies to the 7.0.7 versions of other Storybook packages, ensuring compatibility across the Storybook ecosystem, while version 7.0.6 carries the 7.0.6 versions. For developers, this means upgrading to 7.0.7 will offer the latest features, bug fixes, and performance improvements within these individual add-ons. Both versions share the same peer dependencies for React and React-DOM, ensuring compatibility with a wide range of React projects. The devDependencies specify typescript and @storybook/vue for development and Vue integration purposes. Essentially, version 7.0.7 is a refinement bringing the components of essentials completely up-to-date within the Storybook framework.
All the vulnerabilities related to the version 7.0.7 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.