NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-29775: xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment

criticalCVSS 4.0 9.3GHSA-x3m8-899r-f7c3

Impact An attacker may be able to exploit this vulnerability to bypass authentication or authorization mechanisms in systems that rely on xml-crypto for verifying signed XML documents. The vulnerability allows an attacker to modify a valid signed XML message in a way that still passes signature verification checks.

Published Mar 14, 2025 · Updated Mar 16, 2025

Affected packages

xml-crypto

Ecosystem
npm
Affected
>= 4.0.0, < 6.0.1
Fixed in
6.0.1
Check
npm ls xml-crypto

xml-crypto

Ecosystem
npm
Affected
>= 3.0.0, < 3.2.1
Fixed in
3.2.1
Check
npm ls xml-crypto

xml-crypto

Ecosystem
npm
Affected
< 2.1.6
Fixed in
2.1.6
Check
npm ls xml-crypto

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

An attacker may be able to exploit this vulnerability to bypass authentication or authorization mechanisms in systems that rely on xml-crypto for verifying signed XML documents. The vulnerability allows an attacker to modify a valid signed XML message in a way that still passes signature verification checks. For example, it could be used to alter critical identity or access control attributes, enabling an attacker to escalate privileges or impersonate another user.

Patches

All versions <= 6.0.0 are affected. Please upgrade to version 6.0.1.

If you are still using v2.x or v3.x please upgrade to the associated patch version.

Indicators of Compromise

When logging XML payloads, check for the following indicators. If the payload includes encrypted elements, ensure you analyze the decrypted version for a complete assessment. (If encryption is not used, analyze the original XML document directly). This applies to various XML-based authentication and authorization flows, such as SAML Response payloads.

Presence of Comments in DigestValue

A DigestValue should not contain comments. If you find comments within it, this may indicate tampering.

Example of a compromised `DigestValue`:

<DigestValue>
    <!--TBlYWE0ZWM4ODI1NjliYzE3NmViN2E1OTlkOGDhhNmI=-->
    c7RuVDYo83z2su5uk0Nla8DXcXvKYKgf7tZklJxL/LZ=
</DigestValue>

Code to test

Pass in the decrypted version of the document

decryptedDocument = ... // yours to implement

const digestValues = xpath.select(
  "//*[local-name()='DigestValue'][count(node()) > 1]",
  decryptedDocument,
);

if (digestValues.length > 0) {
  // Compromise detected, yours to implement
}

Credited to ahacker1-securesaml, marktran, mattgd, blairworkos, mthadley, nickcollisson-workos, latacora-paul.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries