EudorIACyber Intelligence
Monitoraggio operativo Newsletter IT EN
← Torna all'intelligence
Vulnerabilità

CVE-2025-12999: UrlUtil.getBaseUrl builds the absolute URLs in a response — download links, icons, asset and API URLs — from the X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix request headers, with no check on whether the se

Fonte ufficiale
Sintesi operativa EudorIA

Cosa significa

Priorità 85/100

NIST National Vulnerability Database ha pubblicato CVE-2025-12999. La rilevanza va confermata rispetto alle tecnologie effettivamente in uso.

Perché conta

Il segnale diventa operativo solo se prodotto, versione o servizio sono presenti nel perimetro.

DestinatariITSOCCISO
Centro informazioni

Traduzione in elaborazione

NIST National Vulnerability Database

Il contenuto ufficiale è disponibile nella lingua originale. La versione italiana verrà pubblicata al termine dei controlli automatici.

Testo acquisito dalla fonte

UrlUtil.getBaseUrl builds the absolute URLs in a response — download links, icons, asset and API URLs — from the X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix request headers, with no check on whether the sender was a trusted proxy, falling back to the client-supplied Host header. Those responses are cached under keys that do not include the host (extension.json since 0.6.0, namespace.details.json since 0.9.0, sitemap since 0.14.5, latest.extension.version.vscode since 0.34.2). A single request carrying a forged header therefore places attacker-chosen URLs into an entry served to every other client for the lifetime of that entry — one hour by default, and cluster-wide where ovsx.redis.enabled is set. The VSIX download URL, its signature URL and the public key URL are all derived from the same base URL, so extension signing does not limit the impact: an attacker who poisons an entry supplies the package, the signature over it, and the key used to verify it. Exploitability depends on deployment topology. A server reachable directly by clients, or fronted by a proxy that relays the client's X-Forwarded-Host rather than overwriting it, is exploitable by an unauthenticated remote attacker. A proxy that overwrites the header is not. An unauthenticated attacker can poison Open VSX's per-extension metadata cache with attacker-controlled download, signature, and public-key URLs by supplying a crafted X-Forwarded-Host header, causing downstream VS Code-compatible editors to fetch and install a malicious VSIX. Workarounds (unpatched versions) 1. Configure the reverse proxy to set rather than relay X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix — note that nginx's $host is the client's Host header and is not a safe value. 2. Ensure the server is not reachab

Fonte
NIST National Vulnerability Database
Entità pubblicatrice
NIST National Vulnerability Database
Tipo entità
Autorità nazionale
Area
North America · US
Lingua originale
en · traduzione in preparazione
Pubblicazione
21/09/2026 11:17
CVE
CVE-2025-12999
Classificazione
Critica
Paese indicato
US
Perimetro tecnico

Prodotti e versioni interessati

Non pubblicati
Nessun intervallo strutturato pubblicato.

Le fonti ufficiali interrogate non espongono ancora un elenco di versioni interessate. Non viene effettuata alcuna deduzione automatica.

Apri la fonte originale