CVE-2025-61925

{"id": "CVE-2025-61925", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-61925", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-10-10T20:00:44.551372Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 2.5, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "withastro", "product": "astro", "versions": [{"status": "affected", "version": "< 5.14.2"}]}]}], "published": "2025-10-10T20:15:38.233", "references": [{"url": "https://github.com/Chisnet/minimal_dynamic_astro_server", "tags": ["Product"], "source": "security-advisories@github.com"}, {"url": "https://github.com/withastro/astro/security/advisories/GHSA-5ff5-9fcw-vg88", "tags": ["Exploit", "Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-470"}]}], "descriptions": [{"lang": "en", "value": "Astro is a web framework. Prior to version 5.14.2, Astro reflects the value in `X-Forwarded-Host` in output when using `Astro.url` without any validation. It is common for web servers such as nginx to route requests via the `Host` header, and forward on other request headers. As such as malicious request can be sent with both a `Host` header and an `X-Forwarded-Host` header where the values do not match and the `X-Forwarded-Host` header is malicious. Astro will then return the malicious value. This could result in any usages of the `Astro.url` value in code being manipulated by a request. For example if a user follows guidance and uses `Astro.url` for a canonical link the canonical link can be manipulated to another site. It is theoretically possible that the value could also be used as a login/registration or other form URL as well, resulting in potential redirecting of login credentials to a malicious party. As this is a per-request attack vector the surface area would only be to the malicious user until one considers that having a caching proxy is a common setup, in which case any page which is cached could persist the malicious value for subsequent users. Many other frameworks have an allowlist of domains to validate against, or do not have a case where the headers are reflected to avoid such issues. This could affect anyone using Astro in an on-demand/dynamic rendering mode behind a caching proxy. Version 5.14.2 contains a fix for the issue."}, {"lang": "es", "value": "Astro es un framework web. Antes de la versi\u00f3n 5.14.2, Astro refleja el valor en 'X-Forwarded-Host' en la salida al usar 'Astro.url' sin ninguna validaci\u00f3n. Es com\u00fan que los servidores web como nginx enruten las solicitudes a trav\u00e9s del encabezado 'Host' y reenv\u00eden otros encabezados de solicitud. Como tal, se puede enviar una solicitud maliciosa con un encabezado 'Host' y un encabezado 'X-Forwarded-Host' donde los valores no coinciden y el encabezado 'X-Forwarded-Host' es malicioso. Astro devolver\u00e1 entonces el valor malicioso. Esto podr\u00eda resultar en que cualquier uso del valor 'Astro.url' en el c\u00f3digo sea manipulado por una solicitud. Por ejemplo, si un usuario sigue las indicaciones y usa 'Astro.url' para un enlace can\u00f3nico, el enlace can\u00f3nico puede ser manipulado a otro sitio. Es te\u00f3ricamente posible que el valor tambi\u00e9n pueda usarse como una URL de inicio de sesi\u00f3n/registro u otra URL de formulario, lo que resultar\u00eda en el posible redireccionamiento de las credenciales de inicio de sesi\u00f3n a una parte maliciosa. Dado que este es un vector de ataque por solicitud, la superficie de ataque solo ser\u00eda para el usuario malicioso hasta que se considere que tener un proxy de almacenamiento en cach\u00e9 es una configuraci\u00f3n com\u00fan, en cuyo caso cualquier p\u00e1gina que se almacene en cach\u00e9 podr\u00eda persistir el valor malicioso para usuarios posteriores. Muchos otros frameworks tienen una lista de permitidos de dominios para validar, o no tienen un caso en el que los encabezados se reflejen para evitar tales problemas. Esto podr\u00eda afectar a cualquiera que use Astro en un modo de renderizado bajo demanda/din\u00e1mico detr\u00e1s de un proxy de almacenamiento en cach\u00e9. La versi\u00f3n 5.14.2 contiene una soluci\u00f3n para el problema."}], "lastModified": "2026-10-08T13:10:00.200", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:astro:astro:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "FFAAA369-C462-46C6-8029-8ADC566A1869", "versionEndExcluding": "5.14.2"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}