@storybook/react version 7.6.8 represents a minor update over version 7.6.7, offering subtle yet important refinements for React Storybook users. Examining the dependencies, the core changes appear to be within Storybook's internal packages. Specifically, dependencies such as @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.6.7 to 7.6.8. These updates likely encompass bug fixes, performance enhancements, and potentially new features or API adjustments within Storybook's architecture.
While the direct impact on the React components and stories developers write might not be immediately apparent, these internal updates are crucial for maintaining the stability, performance, and overall user experience of Storybook. In terms of peer dependencies and other core dependencies, there are no major changes, meaning developers can upgrade from 7.6.7 to 7.6.8 without worrying about conflicts with their existing React, React DOM, or TypeScript versions.
The primary benefit of upgrading lies in leveraging the cumulative improvements incorporated into Storybook's core modules. These improvements can translate into more reliable documentation generation, smoother interaction with the Storybook UI, and enhanced debugging capabilities. Notably, both versions share identical development dependencies and a consistent set of core dependencies which suggests a focus on refining existing features and ensuring seamless integration across different configurations. The newer version has a release date approximately ten days after the older one, indicating a quick fix release cycle.
All the vulnerabilities related to the version 7.6.8 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.