CVE-2024-39315

{"id": "CVE-2024-39315", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.7, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.1}]}, "published": "2024-07-02T20:15:06.110", "references": [{"url": "https://github.com/pomerium/pomerium/commit/4c7c4320afb2ced70ba19b46de1ac4383f3daa48", "source": "security-advisories@github.com"}, {"url": "https://github.com/pomerium/pomerium/security/advisories/GHSA-rrqr-7w59-637v", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-201"}]}], "descriptions": [{"lang": "en", "value": "Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, the Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users. This issue may be more severe in the presence of a cross-site scripting vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the `/.pomerium` endpoint. Upstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner. Note that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided the application verifies the Pomerium JWT for each request, the connection between Pomerium and the application is secured by mTLS, or the connection between Pomerium and the application is otherwise secured at the network layer. The issue is patched in Pomerium v0.26.1. No known workarounds are available."}, {"lang": "es", "value": "Pomerium es un proxy de acceso consciente de la identidad y el contexto. Antes de la versi\u00f3n 0.26.1, la p\u00e1gina de informaci\u00f3n del usuario de Pomerium (en `/.pomerium`) inclu\u00eda involuntariamente tokens de ID y acceso OAuth2 serializados de la sesi\u00f3n del usuario que hab\u00eda iniciado sesi\u00f3n. Estos tokens no est\u00e1n destinados a ser expuestos a los usuarios finales. Este problema puede ser m\u00e1s grave en presencia de una vulnerabilidad de cross-site scripting en una aplicaci\u00f3n ascendente enviada a trav\u00e9s de Pomerium. Si un atacante pudiera insertar un script malicioso en una p\u00e1gina web proxy a trav\u00e9s de Pomerium, ese script podr\u00eda acceder a estos tokens realizando una solicitud al endpoint `/.pomerium`. Las aplicaciones ascendentes que autentican solo el token de ID pueden ser vulnerables a la suplantaci\u00f3n del usuario utilizando un token obtenido de esta manera. Tenga en cuenta que un token de acceso OAuth2 o un token de identificaci\u00f3n por s\u00ed solo no es suficiente para secuestrar la sesi\u00f3n de Pomerium de un usuario. Las aplicaciones ascendentes no deben ser vulnerables a la suplantaci\u00f3n del usuario a trav\u00e9s de estos tokens, siempre que la aplicaci\u00f3n verifique el Pomerium JWT para cada solicitud, la conexi\u00f3n entre Pomerium y la aplicaci\u00f3n est\u00e9 protegida por mTLS, o la conexi\u00f3n entre Pomerium y la aplicaci\u00f3n est\u00e9 asegurada de otro modo en la capa de red. . El problema se solucion\u00f3 en Pomerium v0.26.1. No hay workarounds disponibles."}], "lastModified": "2024-07-03T12:53:24.977", "sourceIdentifier": "security-advisories@github.com"}