CVE-2025-64186

{"id": "CVE-2025-64186", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-64186", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2025-11-14T17:40:02.222557Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.7, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 2.3}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "evervault", "product": "evervault-go", "versions": [{"status": "affected", "version": "< 1.3.2"}]}]}], "published": "2025-11-12T21:15:53.727", "references": [{"url": "https://github.com/evervault/evervault-go/commit/7c824d289bba11ec0bea46a338023f5b128bbb28", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/evervault/evervault-go/pull/48", "tags": ["Issue Tracking", "Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/evervault/evervault-go/security/advisories/GHSA-88h9-77c7-p6w4", "tags": ["Exploit", "Vendor Advisory"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-347"}]}], "descriptions": [{"lang": "en", "value": "Evervault is a payment security solution. A vulnerability was identified in the `evervault-go` SDK\u2019s attestation verification logic in versions of `evervault-go` prior to 1.3.2 that may allow incomplete documents to pass validation. This may cause the client to trust an enclave operator that does not meet expected integrity guarantees. The exploitability of this issue is limited in Evervault-hosted environments as an attacker would require the pre-requisite ability to serve requests from specific evervault domain names, following from our ACME challenge based TLS certificate acquisition pipeline. The vulnerability primarily affects applications which only check PCR8. Though the efficacy is also reduced for applications that check all PCR values, the impact is largely remediated by checking PCR 0, 1 and 2. The identified issue has been addressed in version 1.3.2 by validating attestation documents before storing in the cache, and replacing the naive equality checks with a new SatisfiedBy check. Those who useevervault-go to attest Enclaves that are hosted outside of Evervault environments and cannot upgrade have two possible workarounds available. Modify the application logic to fail verification if PCR8 is not explicitly present and non-empty and/or add custom pre-validation to reject documents that omit any required PCRs."}, {"lang": "es", "value": "Evervault es una soluci\u00f3n de seguridad de pagos. Se identific\u00f3 una vulnerabilidad en la l\u00f3gica de verificaci\u00f3n de atestaci\u00f3n del SDK 'evervault-go' en versiones de 'evervault-go' anteriores a la 1.3.2 que puede permitir que documentos incompletos pasen la validaci\u00f3n. Esto puede causar que el cliente conf\u00ede en un operador de enclave que no cumple con las garant\u00edas de integridad esperadas. La explotabilidad de este problema es limitada en entornos alojados por Evervault, ya que un atacante requerir\u00eda la capacidad pre-requisito de servir solicitudes desde nombres de dominio espec\u00edficos de evervault, siguiendo nuestra cadena de adquisici\u00f3n de certificados TLS basada en el desaf\u00edo ACME. La vulnerabilidad afecta principalmente a las aplicaciones que solo verifican PCR8. Aunque la eficacia tambi\u00e9n se reduce para las aplicaciones que verifican todos los valores de PCR, el impacto se remedia en gran medida al verificar PCR 0, 1 y 2. El problema identificado se ha abordado en la versi\u00f3n 1.3.2 validando los documentos de atestaci\u00f3n antes de almacenarlos en la cach\u00e9 y reemplazando las comprobaciones de igualdad ingenuas con una nueva comprobaci\u00f3n SatisfiedBy. Aquellos que usan 'evervault-go' para atestiguar Enclaves que est\u00e1n alojados fuera de los entornos de Evervault y no pueden actualizar tienen dos posibles soluciones alternativas disponibles. Modificar la l\u00f3gica de la aplicaci\u00f3n para que la verificaci\u00f3n falle si PCR8 no est\u00e1 expl\u00edcitamente presente y no vac\u00edo y/o a\u00f1adir una pre-validaci\u00f3n personalizada para rechazar documentos que omitan cualquier PCR requerido."}], "lastModified": "2026-10-18T20:10:00.110", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:evervault:evervault:*:*:*:*:*:go:*:*", "vulnerable": true, "matchCriteriaId": "4E2CDCE3-4441-41C9-A947-3437A3465C13", "versionEndExcluding": "1.3.2"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}