First published: Mon Mar 17 2025(Updated: )
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 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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
CryptoLib | <=1.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-29910 is classified as a high-severity vulnerability due to its potential impact on communication security.
To fix CVE-2025-29910, update CryptoLib to version 1.3.4 or later, which addresses the memory leak issue.
CVE-2025-29910 affects CryptoLib versions up to and including 1.3.3.
The risks associated with CVE-2025-29910 include potential disruption of secure communications between spacecraft and ground stations.
As of now, there is no public indication that CVE-2025-29910 is being actively exploited in the wild.