CVE-2024-32962: Xml crypto Xml-crypto Vulnerable To XML Signature Vulnerability
CRITICALCVE-2024-32962 is a CRITICAL (CVSS 10.0) xml-crypto vulnerable to xml signature vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Xml crypto libraries in the npm ecosystem. The issue involves xml-crypto vulnerable to xml signature verification bypass due improper verification of signature/signature spoofing. Remediation is available by upgrading affected packages to version 6.0.0.
CVE-2024-32962 at a Glance
Security Impact
CVSS: 10.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).
How to Fix CVE-2024-32962
To remediate this vulnerability, upgrade all affected Xml crypto dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install xml-crypto@6.0.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls xml-crypto
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2024-32962, inspect your project dependencies using npm:
npm ls xml-crypto
Analyze the terminal output to locate any version of Xml crypto in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.0.0), your application is affected.
Note: The npm ls xml-crypto command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Xml crypto, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-32962 Affected Xml crypto Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
xml-crypto
|
npm |
≥ 4.0.0
< 6.0.0
|
6.0.0
|
References
Frequently Asked Questions
What is CVE-2024-32962?
Which Xml crypto versions are affected?
What version fixes CVE-2024-32962?
Is xml-crypto affected?
What is the CVSS score of CVE-2024-32962?
What CWE is associated with CVE-2024-32962?
How can I check npm dependencies for CVE-2024-32962?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2xp3-57p7-qf4v",
"modified" : "2024-07-05T18:34:13Z",
"published" : "2024-05-01T17:05:53Z",
"aliases" : [ "CVE-2024-32962" ],
"summary" : "xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing",
"details" : "### Summary\n\nDefault configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a `<KeyInfo />` element, and pass `xml-crypto` default validation checks.\n\n### Details\n\nAffected `xml-crypto` versions between versions `>= 4.0.0` and `< 6.0.0`. \n\n`xml-crypto` trusts by default any certificate provided via digitally signed XML document's `<KeyInfo />`.\n\n`xml-crypto` prefers to use any certificate provided via digitally signed XML document's `<KeyInfo />` even if library was configured to use specific certificate (`publicCert`) for signature verification purposes.\n\nAttacker can spoof signature verification by modifying XML document and replacing existing signature with signature generated with malicious private key (created by attacker) and by attaching that private key's certificate to `<KeyInfo />` element.\n\nVulnerability is combination of changes introduced to `4.0.0` at\n* https://github.com/node-saml/xml-crypto/pull/301\n* https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11ca\n\nChanges at PR provided default method to extract certificate from signed XML document.\n* https://github.com/node-saml/xml-crypto/blob/c2b83f984049edb68ad1d7c6ad0739ec92af11ca/lib/signed-xml.js#L405-L414\n* https://github.com/node-saml/xml-crypto/blob/c2b83f984049edb68ad1d7c6ad0739ec92af11ca/lib/signed-xml.js#L334\n\nand changes at PR prefer output of that method to be used as certificate for signature verification even in the case when library is configured to use specific/pre-configured `signingCert`\n* https://github.com/node-saml/xml-crypto/blob/c2b83f984049edb68ad1d7c6ad0739ec92af11ca/lib/signed-xml.js#L507\n\nName of the `signingCert` was changed later (but prior to `4.0.0` release) to `publicCert`:\n* https://github.com/node-saml/xml-crypto/commit/78329fbae34c9b25ba25882604e960f506d7c0e7\n* https://github.com/node-saml/xml-crypto/blob/78329fbae34c9b25ba25882604e960f506d7c0e7/lib/signed-xml.js#L507\n\nIssue was fixed to `6.0.0` by disabling implicit usage of default `getCertFromKeyInfo` implementation:\n* https://github.com/node-saml/xml-crypto/pull/445\n* https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000\n\nPossible workarounds for versions 4.x and 5.x:\n- Check the certificate extracted via `getCertFromKeyInfo` against trusted certificates before accepting the results of the validation.\n- Set `xml-crypto`'s `getCertFromKeyInfo` to `() => undefined` forcing `xml-crypto` to use an explicitly configured `publicCert` or `privateKey` for signature verification.\n\n### PoC\n\nhttps://github.com/node-saml/xml-crypto/discussions/399\n\n### Impact\n\nAn untrusted certificate can be used to pass a malicious XML payload through an improperly configured installation of `xml-crypto`.\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "xml-crypto"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "6.0.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-32962"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/pull/301"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/pull/445"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11ca"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/node-saml/xml-crypto"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/discussions/399"
}, {
"type" : "WEB",
"url" : "https://security.netapp.com/advisory/ntap-20240705-0003"
}, {
"type" : "WEB",
"url" : "https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-347" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2024-05-01T17:05:53Z",
"nvd_published_at" : "2024-05-02T07:15:21Z"
}
}