CVE-2024-32962
published 2024-05-02CVE-2024-32962: xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the…
PriorityP259critical10CVSS 3.1
AVNACLPRNUINSCCHIHAN
EPSS
0.83%
53.0th percentile
xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of the w3 xmldsig-core-20080610 spec. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a `` element, and pass `xml-crypto` default validation checks. As a result `xml-crypto` trusts by default any certificate provided via digitally signed XML document's ``. `xml-crypto` prefers to use any certificate provided via digitally signed XML document's `` even if library was configured to use specific certificate (`publicCert`) for signature verification purposes. An attacker 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 `` element. This vulnerability is combination of changes introduced to `4.0.0` on pull request 301 / commit `c2b83f98` and has been addressed in version 6.0.0 with pull request 445 / commit `21201723d`. Users are advised to upgrade. Users unable to upgrade may either check the certificate extracted via `getCertFromKeyInfo` against trusted certificates before accepting the results of the validation or set `xml-crypto's getCertFromKeyInfo` to `() => undefined` forcing `xml-crypto` to use an explicitly configured `publicCert` or `privateKey` for signature verification.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| node-saml | xml-crypto | — | — |
| node-saml | xml-crypto | >= 4.0.0 < 6.0.0 | 6.0.0 |
Detection & IOCsextracted from sources · hover to see the quote
- →Detect xml-crypto versions between 4.0.0 (inclusive) and 6.0.0 (exclusive) as vulnerable; the regression was introduced in commit c2b83f98 (PR 301) and fixed in commit 21201723d (PR 445) ↗
- ·The vulnerable behaviour is the DEFAULT configuration of xml-crypto (versions >=4.0.0 <6.0.0); no special attacker-controlled configuration is required — any consumer relying on default validation is affected ↗
- ·Workaround 1: validate the certificate returned by `getCertFromKeyInfo` against a trusted certificate store before accepting validation results ↗
- ·Workaround 2: set `getCertFromKeyInfo` to `() => undefined` to force xml-crypto to use the explicitly configured `publicCert` or `privateKey` instead of the attacker-supplied certificate in `<KeyInfo>` ↗
CVSS provenance
nvdv3.110.0CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
vendor_redhat10.0CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
osv·2024-05-01
CVE-2024-32962 [CRITICAL] xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
### Summary
Default 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 `` element, and pass `xml-crypto` default validation checks.
### Details
Affected `xml-crypto` versions between versions `>= 4.0.0` and ``.
`xml-crypto` prefers to use any certificate provided via digitally signed XML document's `` even if library was configured to use specific certificate (`publicCert`) fo
GHSA
xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
ghsa·2024-05-01
CVE-2024-32962 [CRITICAL] CWE-347 xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing
### Summary
Default 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 `` element, and pass `xml-crypto` default validation checks.
### Details
Affected `xml-crypto` versions between versions `>= 4.0.0` and ``.
`xml-crypto` prefers to use any certificate provided via digitally signed XML document's `` even if library was configured to use specific certificate (`publicCert`) fo
Red Hat
xml-crypto: XML signature verification bypass due improper verification of signature / signature spoofing
vendor_redhat·2024-05-02·CVSS 10.0
CVE-2024-32962 [CRITICAL] CWE-347 xml-crypto: XML signature verification bypass due improper verification of signature / signature spoofing
xml-crypto: XML signature verification bypass due improper verification of signature / signature spoofing
xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of the w3 xmldsig-core-20080610 spec. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a `` element, and pass `xml-crypto` default validation checks. As a result `xml-crypto` trusts by default any certificate provided via digitally signed XML document's ``. `xml-crypto` prefers to use any certificate provided via digitally signed XML document's `` even if libra
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11cahttps://github.com/node-saml/xml-crypto/pull/301https://github.com/node-saml/xml-crypto/pull/445https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4vhttps://security.netapp.com/advisory/ntap-20240705-0003/https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidationhttps://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11cahttps://github.com/node-saml/xml-crypto/pull/301https://github.com/node-saml/xml-crypto/pull/445https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4vhttps://security.netapp.com/advisory/ntap-20240705-0003/https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation
2024-05-02
Published