CVE-2025-64096: CryptoLib vulnerable to Stack Buffer Overflow in Crypto_Key_Update due to missing TLV length check
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. Prior to 1.4.2, there is a missing bounds check in CryptoKeyupdate() (cryptokeymgmt.c) which allows a remote attacker to trigger a stack-based buffer overflow by supplying a TLV packet with a spoofed length field. The function calculates the number of keys from an attacker-controlled field (pdulen), which may exceed the static array size (kblk[98]), leading to an out-of-bounds write and potential memory corruption. This vulnerability is fixed in 1.4.2.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64096?
CVE-2025-64096 has a high severity rating due to the critical nature of the missing bounds check in the CryptoLib.
How do I fix CVE-2025-64096?
To fix CVE-2025-64096, upgrade CryptoLib to version 1.4.2 or later.
What products are affected by CVE-2025-64096?
CVE-2025-64096 affects versions of CryptoLib prior to 1.4.2.
What type of vulnerability is CVE-2025-64096?
CVE-2025-64096 is a security vulnerability related to cryptographic implementation flaws.
Who is the vendor for CVE-2025-64096?
The vendor for CVE-2025-64096 is CryptoLib.