The @storybook/addon-essentials package provides a suite of essential add-ons that significantly enhance the Storybook development experience. Comparing versions 7.6.15 and 7.6.14 reveals a focused update strategy primarily centered around maintaining consistency and potentially addressing bug fixes or minor improvements.
Both versions share the same core set of dependencies, including vital add-ons like @storybook/addon-docs for generating documentation, @storybook/addon-controls for interactive component property manipulation, and add-ons for actions, measure, outline, toolbars, viewport, highlight, and backgrounds. These tools collectively streamline the UI development workflow within Storybook. The consistent dependency versions across the critical add-ons indicate a focus on stability and reliability.
The development dependencies, specifically typescript and @storybook/vue, also remain consistent, suggesting no significant changes in the underlying build process or Vue.js integration. Furthermore, the peer dependencies for React and React DOM remain unchanged, ensuring compatibility with a wide range of React projects using versions 16.8.0 through 18.0.0.
The key difference lies in the releaseDate, with version 7.6.15 released three days after 7.6.14. This is probably a patch release, implying bug fixes or minor enhancements rather than substantial feature additions. For developers, this update ensures you're using the most up-to-date and potentially more stable version of the essentials package. Developers should consider upgrading to 7.6.15 to benefit from the latest patches and ensure compatibility within their Storybook environment.
All the vulnerabilities related to the version 7.6.15 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.