Raw vector
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:P/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:XSummary
CVE-2025-29909 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Nasa Cryptolib. Its CVSS base score is 8.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 41% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CryptoLib is a software library implementing the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to protect communications between a spacecraft running NASA's core Flight System (cFS) and a ground station. Versions 1.3.3 and earlier contain a heap buffer overflow in the Crypto_TC_ApplySecurity() function, triggered by integer issues (CWE-191) that lead to out-of-bounds writes (CWE-787) when processing incoming Telecommand (TC) frames.
An unauthenticated attacker able to inject crafted TC frames into the processing path can trigger denial of service or, under favorable memory conditions, remote code execution. The flaw affects any ground station, mission control software, or other application that uses CryptoLib for TC handling without performing strict frame validation before calling the vulnerable function.
The project has published a fix in commit c7e8a8745ff4b5e9bd7e500e91358e86d5abedcc, referenced in GitHub Security Advisory GHSA-q2pc-c3jx-3852. Operators are advised to apply the patch and ensure incoming TC frames are validated prior to security processing. The EPSS score has remained in the 0.16–0.20 range with no pronounced post-disclosure climb.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6612
Vulnerability Data
CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. In versions 1.3.3 and prior, a heap…
more
buffer overflow vulnerability in CryptoLib's `Crypto_TC_ApplySecurity()` allows an attacker to craft a malicious TC frame that causes out-of-bounds memory writes. This can result in denial of service (DoS) or, under certain conditions, remote code execution (RCE). Any application or system that relies on CryptoLib for Telecommand (TC) processing and does not strictly validate incoming TC frames is at risk. This includes satellite ground stations or mission control software where attackers can inject malformed frames. A patch is available at commit c7e8a8745ff4b5e9bd7e500e91358e86d5abedcc.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static/dynamic analysis directly find integer underflow defects before code is released.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Security engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer underflow during subtraction.
Input validation can reject or sanitize values that would cause a subtraction to underflow the representable range.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
Routine patching can remediate known underflow bugs once they are discovered in deployed software.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches integer underflow defects before release.
Secure development lifecycle mandates input validation and arithmetic checks that prevent integer underflow.
Application security requirements include bounds checking and safe arithmetic to avoid underflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.
Change management can enforce review gates that catch unsafe memory operations before deployment.