CVE-2025-54887

CVSS v3 9.1 CRITICAL

9.1^/10

CVSS v3 : CRITICAL

Vector :

Exploitability : 3.9 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

j

we is a Ruby implementation of the RFC 7516 JSON Web Encryption (JWE) standard. In versions 1.1.0 and below, authentication tags of encrypted JWEs can be brute forced, which may result in loss of confidentiality for those JWEs and provide ways to craft arbitrary JWEs. This puts users at risk because JWEs can be modified to decrypt to an arbitrary value, decrypted by observing parsing differences and the GCM internal GHASH key can be recovered. Users are affected by this vulnerability even if they do not use an AES-GCM encryption algorithm for their JWEs. As the GHASH key may have been leaked, users must rotate the encryption keys after upgrading. This issue is fixed in version 1.1.1.

References

Link	Resource
https://github.com/jwt/ruby-jwe/commit/1e719d79ba3d7aadaa39a2f08c25df077a0f9ff1
https://github.com/jwt/ruby-jwe/security/advisories/GHSA-c7p4-hx26-pr73

Configurations

No configuration.

History

08 Aug 2025, 20:30

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-08-08 01:15

Updated : 2025-08-08 20:30

NVD link : CVE-2025-54887

Mitre link : CVE-2025-54887

CVE.ORG link : CVE-2025-54887

JSON object : View

Products Affected

No product.

CWE

CWE-354

Improper Validation of Integrity Check Value

{"id": "CVE-2025-54887", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "published": "2025-08-08T01:15:25.287", "references": [{"url": "https://github.com/jwt/ruby-jwe/commit/1e719d79ba3d7aadaa39a2f08c25df077a0f9ff1", "source": "[email protected]"}, {"url": "https://github.com/jwt/ruby-jwe/security/advisories/GHSA-c7p4-hx26-pr73", "source": "[email protected]"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-354"}]}], "descriptions": [{"lang": "en", "value": "jwe is a Ruby implementation of the RFC 7516 JSON Web Encryption (JWE) standard. In versions 1.1.0 and below, authentication tags of encrypted JWEs can be brute forced, which may result in loss of confidentiality for those JWEs and provide ways to craft arbitrary JWEs. This puts users at risk because JWEs can be modified to decrypt to an arbitrary value, decrypted by observing parsing differences and the GCM internal GHASH key can be recovered. Users are affected by this vulnerability even if they do not use an AES-GCM encryption algorithm for their JWEs. As the GHASH key may have been leaked, users must rotate the encryption keys after upgrading. This issue is fixed in version 1.1.1."}, {"lang": "es", "value": "jwe es una implementaci\u00f3n en Ruby del est\u00e1ndar RFC 7516 JSON Web Encryption (JWE). En las versiones 1.1.0 y anteriores, las etiquetas de autenticaci\u00f3n de los JWE cifrados pueden ser atacadas por fuerza bruta, lo que puede resultar en la p\u00e9rdida de confidencialidad de dichos JWE y permitir la manipulaci\u00f3n de JWE arbitrarios. Esto pone en riesgo a los usuarios, ya que los JWE pueden modificarse para descifrarse a un valor arbitrario, descifrarse observando las diferencias de an\u00e1lisis y recuperar la clave GHASH interna de GCM. Los usuarios se ven afectados por esta vulnerabilidad incluso si no utilizan un algoritmo de cifrado AES-GCM para sus JWE. Dado que la clave GHASH puede haberse filtrado, los usuarios deben rotar las claves de cifrado despu\u00e9s de actualizar. Este problema se solucion\u00f3 en la versi\u00f3n 1.1.1."}], "lastModified": "2025-08-08T20:30:18.180", "sourceIdentifier": "[email protected]"}