CyberRota Analysis
AI-GeneratedNuxt versions 4.4.7 to 4.5.0 and 3.21.7 to 3.21.9 are vulnerable due to an information disclosure flaw in the Chrome DevTools workspace endpoint, allowing unauthenticated attackers on the same local network to exploit a misconfigured Host header and access sensitive project filesystem paths and UUIDs. This vulnerability poses a medium risk, particularly for developers running the Nuxt development server on network-accessible interfaces with default settings enabled. Organizations using affected versions in development environments should prioritize upgrading to the patched versions 4.5.1 or 3.21.10 to mitigate potential exposure.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Nuxt versions >= 4.4.7 and < 4.5.1, and >= 3.21.7 and < 3.21.10, contain an information disclosure vulnerability in the development server's Chrome DevTools workspace endpoint (GET /.well-known/appspecific/com.chrome.devtools.json). The endpoint's local-request gate (isLocalDevRequest) is header-based and trusts the attacker-supplied Host header rather than the connected peer address. When the dev server is bound to a network-reachable interface (e.g. nuxt dev --host) and experimental.chromeDevtoolsProjectSettings is enabled (the default), an unauthenticated attacker on the LAN can send a request with a spoofed Host header and no browser-specific headers (Sec-Fetch-Site, Origin, Referer) to retrieve the project's absolute filesystem root path (rootDir) and a persistent per-project workspace UUID. Production builds are unaffected. Fixed in 4.5.1 and 3.21.10.