CVE-2025-32965

{"id": "CVE-2025-32965", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-04-22T21:15:45.503", "references": [{"url": "https://github.com/XRPLF/xrpl.js/security/advisories/GHSA-33qr-m49q-rxfx", "source": "security-advisories@github.com"}, {"url": "https://www.aikido.dev/blog/xrp-supplychain-attack-official-npm-package-infected-with-crypto-stealing-backdoor", "source": "security-advisories@github.com"}, {"url": "https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair", "source": "security-advisories@github.com"}, {"url": "https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-506"}]}], "descriptions": [{"lang": "en", "value": "xrpl.js is a JavaScript/TypeScript API for interacting with the XRP Ledger in Node.js and the browser. Versions 4.2.1, 4.2.2, 4.2.3, and 4.2.4 of xrpl.js were compromised and contained malicious code designed to exfiltrate private keys. Version 2.14.2 is also malicious, though it is less likely to lead to exploitation as it is not compatible with other 2.x versions. Anyone who used one of these versions should stop immediately and rotate any private keys or secrets used with affected systems. Users of xrpl.js should pgrade to version 4.2.5 or 2.14.3 to receive a patch. To secure funds, think carefully about whether any keys may have been compromised by this supply chain attack, and mitigate by sending funds to secure wallets, and/or rotating keys. If any account's master key is potentially compromised, disable the key."}, {"lang": "es", "value": "xrpl.js es una API de JavaScript/TypeScript para interactuar con el Libro Mayor de XRP en Node.js y el navegador. Las versiones 4.2.1, 4.2.2, 4.2.3 y 4.2.4 de xrpl.js fueron comprometidas y conten\u00edan c\u00f3digo malicioso dise\u00f1ado para exfiltrar claves privadas. La versi\u00f3n 2.14.2 tambi\u00e9n es maliciosa, aunque es menos probable que resulte en explotaci\u00f3n, ya que no es compatible con otras versiones 2.x. Cualquiera que haya usado una de estas versiones debe detener su uso inmediatamente y rotar las claves privadas o secretos utilizados en los sistemas afectados. Los usuarios de xrpl.js deben actualizar a la versi\u00f3n 4.2.5 o 2.14.3 para recibir un parche. Para proteger los fondos, considere cuidadosamente si alguna clave pudo haber sido comprometida por este ataque a la cadena de suministro y mitigue el riesgo enviando fondos a billeteras seguras o rotando las claves. Si la clave maestra de alguna cuenta est\u00e1 potencialmente comprometida, desact\u00edvela."}], "lastModified": "2025-04-23T14:08:13.383", "sourceIdentifier": "security-advisories@github.com"}