@storybook/addon-essentials is a curated set of Storybook addons designed to enhance the development and presentation of UI components. Version 7.6.9, released on January 17, 2024, offers subtle improvements over its predecessor, version 7.6.8, released just five days prior on January 12, 2024. While the core functionality remains consistent, evidenced by the identical list of dependencies like @storybook/addon-docs, @storybook/addon-controls, and @storybook/addon-actions, both versions ensure compatibility with React versions 16.8.0 through 18.0.0. This makes it a reliable choice for a wide range of React projects.
The lack of significant changes in dependencies suggests that version 7.6.9 likely includes bug fixes or minor performance enhancements that don't necessitate dependency updates. Developers can expect a stable and consistent experience when upgrading from 7.6.8 to 7.6.9. Both versions bundle TypeScript support for Vue, making them suitable for projects utilizing Vue with Storybook. The addon's MIT license promotes ease of use in various projects. Developers already using Storybook and @storybook/addon-essentials may consider updating to the latest version to leverage any incremental improvements and benefit from the most recent bug fixes. The consistent file count and unpacked size between versions also hints at under-the-hood optimizations rather than major feature additions.
All the vulnerabilities related to the version 7.6.9 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.