CVE-2024-32962
Last modified
CVE-2024-32962 is a critical-severity vulnerability rated 10/10 on the CVSS scale. 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. EPSS estimates a 0.83% chance of exploitation in the next 30 days.
Description
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 `<KeyInfo />` 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 `<KeyInfo />`. `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. 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 `<KeyInfo />` 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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2024-32962?
How severe is CVE-2024-32962?
How do I fix CVE-2024-32962?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-32957Missing Authorization vulnerability in Live Composer Team Pa…4.7
- CVE-2024-32958Cross-Site Request Forgery (CSRF) vulnerability in Giorgos S…7.1
- CVE-2024-32959Incorrect Privilege Assignment vulnerability in Sirv CDN and…8.8
- CVE-2024-3296A timing-based side-channel flaw exists in the rust-openssl …5.9
- CVE-2024-32960Improper Privilege Management vulnerability in Booking Ultra…8.8
- CVE-2024-32961Improper Neutralization of Input During Web Page Generation …5.4
- CVE-2024-32963Navidrome is an open source web-based music collection serve…4.2
- CVE-2024-32964Lobe Chat is a chatbot framework that supports speech synthe…9
- CVE-2024-32965Lobe Chat is an open-source, AI chat framework. Versions of …8.6
- CVE-2024-32966Static Web Server (SWS) is a tiny and fast production-ready …5.8
- CVE-2024-32967Zitadel is an open source identity management system. In cas…5.3
- CVE-2024-32969vantage6 is an open-source infrastructure for privacy preser…2.7
Are you affected by CVE-2024-32962?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
