> CVE-2024-32962 [CRITICAL]

« BACK_TO_HOME
PUBLISHED
2024-05-02 07:15
MODIFIED
2024-11-21 09:16
CVSS_SCORE V3
10.0
EPSS (Prob. Exploit)
0.83%
Top 42.1%
DATA SOURCES:
NVD đź”— 2025-10-18 CVE PROJECT đź”— 2026-01-19 FIRST EPSS đź”— 2026-11-08 GITHUB đź”— 2026-11-11 OSV đź”— 2026-11-08

> 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.

> AFFECTED_PRODUCTS

ℹ️ Aucun produit affecté n'a encore été publié par NVD pour cette CVE.

> CVSS V3 METRICS

CVSS_VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

> MÉTRIQUES CVSS DÉTAILLÉES

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Métrique Valeur Interprétation
AV (Vecteur d'Attaque)
Attack Vector
Network (N)
Exploit possible à distance via réseau (HTTP, API, etc.)
AC (Complexité d'Attaque)
Attack Complexity
Low (L)
Peu de conditions requises pour exploiter
PR (Privilèges Requis)
Privileges Required
None (N)
Aucune authentification requise
UI (Interaction Utilisateur)
User Interaction
None (N)
Aucune interaction utilisateur nécessaire
S (Périmètre)
Scope
Changed (C)
Impact s'étend au-delà du composant compromis
C (Impact Confidentialité)
Confidentiality Impact
High (H)
Divulgation totale d'informations
I (Impact Intégrité)
Integrity Impact
High (H)
Modification totale des données possible
A (Impact Disponibilité)
Availability Impact
None (N)
Aucune interruption de service

> RÉSUMÉ DES IMPACTS

Confidentialité
High
Divulgation totale d'informations
Intégrité
High
Modification totale des données possible
Disponibilité
None
Aucune interruption de service

> GITHUB SECURITY ADVISORY

GHSA-2xp3-57p7-qf4v CRITICAL

xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing

AFFECTED PACKAGES:
NPM / xml-crypto
>= 4.0.0, < 6.0.0
Fixed in: 6.0.0

> OSV (GOOGLE OPEN SOURCE VULNERABILITIES)

XML signature verification bypass due improper verification of signature / signature spoofing

AFFECTED PACKAGES:
Unknown / Unknown
6 versions affected
ALIASES:
GHSA-2xp3-57p7-qf4v

> HISTORIQUE DES MODIFICATIONS

Première apparition
02/05/2024 07:15
Source: NVD
📊 ENRICHISSEMENT 18/10/2025 14:50
CVEPROJECT
Champ modifié: CVE Project
Ancienne valeur:
Non
Nouvelle valeur:
Oui
Total des modifications: 1 Dernière mise à jour: 1 year ago
« BACK_TO_HOME