@storybook/react v7.6.7 is a minor release of the popular Storybook React renderer, building upon the foundation of v7.6.6. Both versions provide developers with the tools to build UI components in isolation, fostering a more organized and efficient development workflow. The core functionality remains consistent: leveraging dependencies like acorn, lodash, and react-element-to-jsx-string to render React components within the Storybook environment. Key peer dependencies like react and react-dom ensure compatibility with existing React projects.
Notable difference is the updated dependencies. While the core dependencies remain largely the same, version 7.6.7 upgrades the internal Storybook packages like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim from version 7.6.6 to 7.6.7. This signifies internal improvements and bug fixes within the Storybook ecosystem, enhancing the overall stability and performance of the React renderer.
Developers upgrading to v7.6.7 can expect a more refined experience due to these internal updates, potentially addressing minor issues or performance bottlenecks encountered in the previous version. Although no specific breaking changes are mentioned highlighting major feature additions, the consistent API ensures a seamless transition for users already familiar with v7.6.6. The library benefits from being Open Source under the MIT license.
All the vulnerabilities related to the version 7.6.7 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.