CryptoLib: Improper Control of Dynamically-Managed Code Resources
CVE-2025-46673 is a critical-severity improper control of dynamically-managed code resources 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.51% 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 | 4.9 | Medium | CNA (mitre.org) |
| CVSS 3.1 | 9.9 | Critical | NVD |
Official description
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).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Dynamically-Managed Code Resources
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
How developers prevent this class of flaw
- For any externally-influenced input, check the input against an allowlist of acceptable values.
- Refactor the code so that it does not need to be dynamically managed.
More Improper Control of Dynamically-Managed Code Resources vulnerabilities (CWE-913)
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 Improper Control of Dynamically-Managed Code Resources vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 8.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.