ghsa-x3m8-899r-f7c3
Vulnerability from github
Published
2025-03-14 17:16
Modified
2025-03-16 21:34
Severity ?
9.3 (Critical) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Summary
xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment
Details

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: xml <DigestValue> <!--TBlYWE0ZWM4ODI1NjliYzE3NmViN2E1OTlkOGDhhNmI=--> c7RuVDYo83z2su5uk0Nla8DXcXvKYKgf7tZklJxL/LZ= </DigestValue>

Code to test

Pass in the decrypted version of the document ```js decryptedDocument = ... // yours to implement

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

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

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "npm",
            name: "xml-crypto",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "4.0.0",
                  },
                  {
                     fixed: "6.0.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "npm",
            name: "xml-crypto",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.0.0",
                  },
                  {
                     fixed: "3.2.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "npm",
            name: "xml-crypto",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.1.6",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2025-29775",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-347",
      ],
      github_reviewed: true,
      github_reviewed_at: "2025-03-14T17:16:47Z",
      nvd_published_at: "2025-03-14T18:15:32Z",
      severity: "CRITICAL",
   },
   details: "# Impact\nAn 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.\n\n# Patches\nAll versions <= 6.0.0 are affected. Please upgrade to version 6.0.1.\n\nIf you are still using v2.x or v3.x please upgrade to the associated patch version.\n\n# Indicators of Compromise\n\nWhen 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.\n\n### Presence of Comments in `DigestValue`\nA `DigestValue` should **not** contain comments. If you find comments within it, this may indicate tampering.\n\n**Example of a compromised `DigestValue`:**\n```xml\n<DigestValue>\n    <!--TBlYWE0ZWM4ODI1NjliYzE3NmViN2E1OTlkOGDhhNmI=-->\n    c7RuVDYo83z2su5uk0Nla8DXcXvKYKgf7tZklJxL/LZ=\n</DigestValue>\n```\n\n### Code to test\n\nPass in the decrypted version of the document\n```js\ndecryptedDocument = ... // yours to implement\n\nconst digestValues = xpath.select(\n  \"//*[local-name()='DigestValue'][count(node()) > 1]\",\n  decryptedDocument,\n);\n\nif (digestValues.length > 0) {\n  // Compromise detected, yours to implement\n}\n```",
   id: "GHSA-x3m8-899r-f7c3",
   modified: "2025-03-16T21:34:52Z",
   published: "2025-03-14T17:16:47Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/security/advisories/GHSA-x3m8-899r-f7c3",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2025-29775",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/commit/28f92218ecbb8dcbd238afa4efbbd50302aa9aed",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/commit/886dc63a8b4bb5ae1db9f41c7854b171eb83aa98",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/commit/8ac6118ee7978b46aa56b82cbcaa5fca58c93a07",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/node-saml/xml-crypto",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/releases/tag/v2.1.6",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/releases/tag/v3.2.1",
      },
      {
         type: "WEB",
         url: "https://github.com/node-saml/xml-crypto/releases/tag/v6.0.1",
      },
      {
         type: "WEB",
         url: "https://workos.com/blog/samlstorm",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: "xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.