The @storybook/react package provides a React renderer for the Storybook UI development environment. Version 7.4.0 was released on August 29, 2023, following version 7.3.2 released on August 18, 2023. Key differences between the versions are primarily focused on internal dependency updates and bug fixes, contributing to an improved developer experience.
Notably, several core Storybook packages were bumped from version 7.3.2 to 7.4.0, including @storybook/types, @storybook/docs-tools, @storybook/core-client, @storybook/preview-api, @storybook/client-logger, and @storybook/react-dom-shim. This signifies updates across various facets of Storybook, potentially introducing new features, performance enhancements, or bug resolutions in documentation generation, core client functionalities, preview handling, logging, and React DOM shimming.
A subtle but potentially impactful change is the update of escodegen from version 2.0.0 to 2.1.0. escodegen is a JavaScript code generator from an abstract syntax tree (AST). This could mean enhanced code generation capabilities or fixes related to code formatting and output.
While the developer dependencies and peer dependencies remain largely consistent, the difference in fileCount and unpackedSize reveals a significant change in file structure or included assets, with 7.4.0 having a considerably reduced footprint. This optimization could lead to faster installation times and a more streamlined development workflow. These updates collectively aim to refine the Storybook experience for React developers, offering a more stable and feature-rich environment for UI component development and testing.
All the vulnerabilities related to the version 7.4.0 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.