@storybook/react version 7.0.15 represents a minor update over its predecessor, version 7.0.14, within the Storybook ecosystem. Both versions serve as renderers for React components within Storybook, providing a crucial bridge for visualizing and developing UI elements in isolation. A primary difference lies in the dependencies' versions; while many remain consistent, dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are bumped from 7.0.14 to 7.0.15. This likely reflects internal updates and bug fixes within those specific Storybook modules.
For developers using Storybook with React, this update ensures access to the latest refinements and potentially addresses issues encountered in the previous release. The core functionality of rendering React components within Storybook remains consistent, preserving existing workflows. However, upgrading to 7.0.15 is advisable to leverage the most stable and performant version of these core dependencies and benefit from improvements throughout the Storybook platform. The releaseDate field indicates version 7.0.15 was released shortly after 7.0.14, suggesting this was more of an urgent patch rather than a delayed feature update. By staying current, developers minimize risk and benefit from a smoother development experience using Storybook.
All the vulnerabilities related to the version 7.0.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.