Storybook React has released version 7.6.11, a minor update over the previous stable version 7.6.10, offering incremental improvements for React component development and documentation. Both versions share a common foundation, providing a robust environment for building UI components in isolation with dependencies like acorn, lodash, and react-element-to-jsx-string ensuring seamless integration with React projects. They maintain the same peer dependencies, supporting React versions 16.8.0 through 18.0.0, and TypeScript.
The core difference lies in updated internal dependencies. While most dependencies remain pinned to the same versions, key Storybook packages such as @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have been bumped from 7.6.10 to 7.6.11. Similarly the @storybook/test devDependency has been incremented. This indicates improvements and bug fixes within Storybook's internal modules. For developers, this means potentially enhanced stability, performance tweaks in documentation generation, core functionalities, and improved client-side logging. The update likely contains subtle refinements that streamline the component development workflow within the Storybook environment. Developers should upgrade to 7.6.11 to benefit from these under-the-hood improvements and ensure compatibility with the latest Storybook ecosystem enhancements.
All the vulnerabilities related to the version 7.6.11 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.