CVE-2025-29911: CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function
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 critical heap buffer overflow vulnerability was identified in the CryptoAOSProcessSecurity function of CryptoLib versions 1.3.3 and prior. This vulnerability allows an attacker to trigger a Denial of Service (DoS) or potentially execute arbitrary code (RCE) by providing a maliciously crafted AOS frame with an insufficient length. The vulnerability lies in the function CryptoAOSProcessSecurity, specifically during the processing of the Frame Error Control Field (FECF). The affected code attempts to read from the pingest buffer at indices currentmanagedparametersstruct.maxframesize - 2 and currentmanagedparametersstruct.maxframesize - 1 without verifying if leningest is sufficiently large. This leads to a heap buffer overflow when leningest is smaller than maxframesize. As of time of publication, no known patched versions exist.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-29911?
The severity of CVE-2025-29911 is critical due to the potential for exploitation via heap buffer overflow.
How do I fix CVE-2025-29911?
To fix CVE-2025-29911, upgrade CryptoLib to version 1.3.4 or later.
What software is affected by CVE-2025-29911?
CVE-2025-29911 affects versions of CryptoLib up to 1.3.3.
What type of vulnerability is CVE-2025-29911?
CVE-2025-29911 is a critical heap buffer overflow vulnerability.
Can CVE-2025-29911 lead to remote code execution?
Yes, CVE-2025-29911 has the potential to allow remote code execution if exploited.