@storybook/react jumps from version 7.5.0 to 7.5.1, representing a minor update within the Storybook ecosystem for React component development. Both versions maintain identical descriptions, positioning themselves as the dedicated renderer for React components within Storybook. The core dependencies remain fundamentally the same, ensuring a consistent experience with vital tools like acorn, lodash, and supporting libraries for JSX handling, code generation, and type safety.
Developers will find the peer dependencies unchanged, continuing to support React versions 16.8.0 through 18.0.0, alongside React DOM and TypeScript, granting flexibility across various project setups. Developer dependencies, crucial for building and testing, also stay consistent, utilizing tools like Babel, expect-type, and jest-specific-snapshot.
The key distinction lies in the updated versions of internal Storybook packages within the dependencies. Specifically, @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim are all bumped from 7.5.0 to 7.5.1. These updates likely incorporate bug fixes, performance enhancements, and potentially minor feature additions within the Storybook infrastructure. The release dates confirm that 7.5.1 came out two days after 7.5.0. While not explicitly detailed, developers can expect a smoother and more reliable experience when using Storybook with React components in version 7.5.1. The file count and unpacked size of the packages remain identical, suggesting the changes do not impact the overall size of the library.
All the vulnerabilities related to the version 7.5.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.