High severity · published Apr 27, 2025
CVE-2025-46672
NASA CryptoLib before 1.3.2 does not check the OTAR crypto function returned status, potentially leading to spacecraft hijacking
8.8
CVSS
0.5%
EPSS
No
On KEV
Description
NASA CryptoLib before 1.3.2 does not check the OTAR crypto function returned status, potentially leading to spacecraft hijacking.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 45% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CR
CryptoLib · NASA
before 1.3.2 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-46672
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-46672
Product
https://github.com/nasa/CryptoLib/compare/v1.3.1...v1.3.2
Product
https://github.com/nasa/CryptoLib/pull/360
Exploit
https://securitybynature.fr/post/hacking-cryptolib/
More from CryptoLib
9.9
CVE-2025-46673
NASA CryptoLib before 1.3.2 does not check whether the SA is in an operational state before use, possibly leading to a bypass of the Space Data Link Security protocol (SDLS)
9.9
CVE-2025-46674
NASA CryptoLib before 1.3.2 uses Extended Procedures that are a Work in Progress (not intended for use during flight), potentially leading to a keystream oracle
9.8
CVE-2025-30356
Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity`
9.8
CVE-2025-29913
CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow
9.8
CVE-2025-29912
CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity