Storybook React sees a minor version bump from 7.3.1 to 7.3.2, presenting subtle yet significant updates for React component development, documentation, and testing. Both versions share a foundational dependency structure, relying on core libraries like acorn, lodash, and react-element-to-jsx-string. They also maintain identical peer dependencies, ensuring compatibility with React versions 16.8.0, 17.0.0, and 18.0.0, alongside TypeScript. The dev dependencies remain the same too.
The key changes reside within the internal Storybook ecosystem. Dependencies like @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim have all been updated from version 7.3.1 to 7.3.2. These updates suggest improvements and bug fixes within Storybook's core functionalities related to type definitions, documentation generation, client-side interactions, and the React DOM environment.
Developers upgrading to 7.3.2 can expect a more refined and stable experience. Although the changes may not be immediately visible, these updates likely address edge cases, improve performance, and enhance the overall developer workflow within Storybook. Upgrading ensures access to the latest bug fixes and potentially new features delivered through the updated core dependencies. Furthermore, staying current allows developers to leverage the most recent improvements in Storybook's tooling for building, testing, and showcasing React components. The release date difference indicates active maintenance and continuous improvement of the library.
All the vulnerabilities related to the version 7.3.2 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.