@storybook/react versions 7.1.1 and 7.1.0 are both Storybook React renderers, essential tools for building UI components in isolation and creating interactive documentation. Comparing the two, version 7.1.1 was released on July 24, 2023, while version 7.1.0 was released on July 18, 2023, indicating a quick follow-up release. The core functionality and dependencies remain largely consistent. Both versions include crucial dependencies like acorn for JavaScript parsing, lodash for utility functions, and react-element-to-jsx-string for converting React elements to JSX strings. Key Storybook dependencies such as @storybook/types, @storybook/docs-tools, @storybook/core-client, and @storybook/preview-api are also present.
A notable difference lies in the specific versions of the internal Storybook packages: version 7.1.1 depends on @storybook/types: 7.1.1, @storybook/docs-tools: 7.1.1, @storybook/core-client: 7.1.1, @storybook/preview-api: 7.1.1, and @storybook/client-logger: 7.1.1, while version 7.1.0 utilizes @storybook/types: 7.1.0, @storybook/docs-tools: 7.1.0, @storybook/core-client: 7.1.0, @storybook/preview-api: 7.1.0, and @storybook/client-logger: 7.1.0. This signals that 7.1.1 includes minor updates and bug fixes within the Storybook ecosystem itself. Another difference appears in the devDependencies where @babel/core has been updated from version ^7.22.0 to ^7.22.9.
For developers, upgrading from 7.1.0 to 7.1.1 is likely beneficial, incorporating the latest refinements and internal library updates within Storybook. Both versions offer the same peer dependency requirements for React and React DOM, supporting versions 16.8.0, 17.0.0, and 18.0.0. This ensures broad compatibility for React projects.
All the vulnerabilities related to the version 7.1.1 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.