CryptoLib: Active Debug Code
CVE-2025-46674 is a critical-severity active debug code vulnerability in CryptoLib from Nasa, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.3.2 as the first without the flaw, so updating CryptoLib to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.61% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update CryptoLib to 1.3.2 or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 3.5 | Low | CNA (mitre.org) |
| CVSS 3.1 | 9.9 | Critical | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Active Debug Code
The product is released with debugging code still enabled or active.
How developers prevent this class of flaw
- Remove debug code before deploying the application.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Technical write-ups (may include proof of concept)
- securitybynature.fr/post/hacking-cryptolib/Exploit, Press/Media Coverage
Other references
Other vulnerabilities in CryptoLib
- 8.7 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.2 High severity
- 7.3 High severity
Recent Active Debug Code vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 7.8 High severity
- 7.2 High severity
- 7.5 High severity
- 7.2 High severity
Spotted an error? Tell us.