Cyber Resilience

CVE-2025-29910

Nasa Cryptolib

Public PoC
Published
17 March 2025
Modified
30 April 2025
Patch / advisory
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:X
EPSS Score 0.0046 38th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2025-29910 is a medium-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Nasa Cryptolib. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 38th percentile by exploit likelihood (below the median); 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.

CVE-2025-29910 is a memory leak vulnerability in the `crypto_handle_incrementing_nontransmitted_counter` function within the `crypto_tc.c` file of NASA's CryptoLib, affecting versions 1.3.3 and prior. CryptoLib implements a software-only solution based on the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between spacecraft running the core Flight System (cFS) and ground stations. The flaw occurs because the function allocates memory using `malloc` without always freeing it, leading to gradual resource exhaustion and degraded system performance, especially in long-running processes or those handling large volumes of data.

The vulnerability has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating it is exploitable over the network with low complexity, no privileges or user interaction required. Any unauthenticated remote attacker who can trigger the affected function—such as by sending crafted telemetry commands or data streams to a system using CryptoLib—can cause continuous memory leaks, resulting in resource exhaustion, reduced performance, and potential denial-of-service (DoS) conditions. Systems processing high-throughput or continuous data streams, like those in space communications, are particularly at risk.

The primary advisory is published on the NASA CryptoLib GitHub security page (GHSA-p38w-p2r8-g6g5). As of the CVE publication on 2025-03-17, no patched versions of CryptoLib were available, and mitigations are not detailed in the provided information; practitioners should monitor the repository for updates and consider workarounds such as limiting exposure to untrusted inputs or restarting affected processes periodically.

EU & UK References

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. A memory leak vulnerability was identified in…

more

the `crypto_handle_incrementing_nontransmitted_counter` function of CryptoLib versions 1.3.3 and prior. This vulnerability can lead to resource exhaustion and degraded system performance over time, particularly in long-running processes or systems processing large volumes of data. The vulnerability is present in the `crypto_handle_incrementing_nontransmitted_counter` function within `crypto_tc.c`. The function allocates memory using `malloc` without ensuring the allocated memory is always freed. This issue can lead to resource exhaustion, reduced system performance, and potentially a Denial of Service (DoS) in environments where CryptoLib is used in long-running processes or with large volumes of data. Any system using CryptoLib, especially those handling high-throughput or continuous data streams, could be impacted. As of time of publication, no known patched versions are available.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22024Same product: Nasa Cryptolib
CVE-2026-22026Same product: Nasa Cryptolib
CVE-2026-22025Same product: Nasa Cryptolib
CVE-2025-29912Same product: Nasa Cryptolib
CVE-2026-22697Same product: Nasa Cryptolib
CVE-2026-21899Same product: Nasa Cryptolib
CVE-2026-21898Same product: Nasa Cryptolib
CVE-2024-44912Same product: Nasa Cryptolib
CVE-2024-44911Same product: Nasa Cryptolib
CVE-2025-30216Same product: Nasa Cryptolib

Affected Assets

nasa
cryptolib
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (static analysis, fuzzing, or runtime leak detection) directly finds missing deallocation.

Requiring documented development standards and tools can mandate memory-management disciplines that avoid leaks at introduction.

Engineering principles applied during development can require explicit resource-release patterns that stop memory leaks from being coded.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

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.

finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References