@storybook/addon-essentials is a crucial package for enhancing Storybook development environments, bundling a suite of popular add-ons that streamline component documentation, interaction, and visual testing. Version 7.6.17 represents a minor update over its predecessor, 7.6.16, primarily focusing on internal dependency synchronization. Diving into the specifics, both versions maintain identical core functionalities, including addon-docs for automated documentation generation, addon-actions for tracking user interactions, and addon-controls for interactive component property manipulation. Addons like addon-measure, addon-outline, addon-toolbars, addon-viewport, addon-highlight, and addon-backgrounds remain consistent, empowering developers with tools for precise visual adjustments and comprehensive testing across different contexts.
The key takeaway for developers is the stability and consistency between the two versions. While 7.6.17 likely incorporates bug fixes and subtle improvements within its dependencies (@storybook/* packages are bumped to 7.6.17), the feature set and overall API remain unchanged. Users can upgrade from 7.6.16 to 7.6.17 with confidence, anticipating a seamless transition and potentially benefiting from under-the-hood enhancements. Both versions are compatible with React versions 16.8.0 through 18.0.0, ensuring wide applicability within modern React projects. The continued reliance on ts-dedent and the TypeScript development environment (typescript: ^4.9.3, @storybook/vue: 7.6.17) reaffirm Storybook's commitment to code quality and developer experience.
All the vulnerabilities related to the version 7.6.17 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.