Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64096: CWE-121: Stack-based Buffer Overflow in nasa CryptoLib

0
High
VulnerabilityCVE-2025-64096cvecve-2025-64096cwe-121
Published: Thu Oct 30 2025 (10/30/2025, 17:09:24 UTC)
Source: CVE Database V5
Vendor/Project: nasa
Product: CryptoLib

Description

CVE-2025-64096 is a high-severity stack-based buffer overflow vulnerability in NASA's CryptoLib prior to version 1. 4. 2. The flaw exists in the Crypto_Key_update() function, where a missing bounds check allows a remote attacker to supply a specially crafted TLV packet with a spoofed length field. This causes an out-of-bounds write to a static array, leading to potential memory corruption. Exploitation requires low privileges but no user interaction and can result in full confidentiality, integrity, and availability compromise. Although no known exploits are currently reported in the wild, affected systems should update to version 1. 4. 2 immediately. European organizations involved in aerospace, satellite communications, or space research using CryptoLib or related CCSDS protocols are at risk.

AI-Powered Analysis

AILast updated: 10/30/2025, 18:40:49 UTC

Technical Analysis

CVE-2025-64096 is a stack-based buffer overflow vulnerability identified in NASA's CryptoLib, a software-only implementation of the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP). This protocol secures communications between spacecraft running the core Flight System (cFS) and ground stations. The vulnerability resides in the Crypto_Key_update() function within crypto_key_mgmt.c, where the function processes a TLV (Type-Length-Value) packet. Specifically, the function calculates the number of keys to update based on an attacker-controlled length field (pdu_len) without performing adequate bounds checking against the fixed-size static array kblk[98]. If pdu_len exceeds the array size, this results in an out-of-bounds write on the stack, causing memory corruption. Such corruption can lead to arbitrary code execution, denial of service, or information disclosure. The vulnerability is remotely exploitable over the network with low attack complexity and does not require user interaction, though it requires some privileges (PR:L). The CVSS v3.0 base score is 8.8, indicating high severity with impacts on confidentiality, integrity, and availability. The flaw was fixed in CryptoLib version 1.4.2. No known exploits have been reported in the wild as of publication. Given CryptoLib's role in securing spacecraft communications, exploitation could compromise mission-critical data and control channels between spacecraft and ground stations.

Potential Impact

For European organizations, especially those engaged in aerospace, satellite communications, and space research, this vulnerability poses a significant risk. Exploitation could allow attackers to gain unauthorized control over spacecraft communication links, potentially leading to data breaches, manipulation of telemetry or command data, and disruption of space missions. Such impacts could affect national security, scientific research, and commercial satellite operations. The confidentiality breach could expose sensitive mission data, while integrity and availability impacts could jeopardize spacecraft operations and safety. Given the critical nature of space systems and their reliance on secure communication protocols like SDLS-EP, this vulnerability could have cascading effects on dependent infrastructure and services. European space agencies, research institutions, and satellite operators using CryptoLib or similar CCSDS protocol implementations must prioritize remediation to prevent exploitation.

Mitigation Recommendations

1. Immediate upgrade to CryptoLib version 1.4.2 or later, which contains the patch fixing the bounds check issue in Crypto_Key_update(). 2. Implement strict input validation and sanity checks on all incoming TLV packets to ensure length fields do not exceed expected bounds, even beyond the patched version. 3. Employ network segmentation and strict access controls to limit exposure of spacecraft communication interfaces to trusted entities only. 4. Monitor network traffic for anomalous or malformed TLV packets that could indicate exploitation attempts. 5. Conduct regular security audits and code reviews of cryptographic libraries and communication protocols used in spacecraft systems. 6. Develop incident response plans specific to spacecraft communication compromise scenarios. 7. Collaborate with vendors and space agencies to share threat intelligence and coordinate patch deployment. 8. Consider hardware-based protections or memory safety techniques (e.g., stack canaries, ASLR) in the deployment environment to mitigate exploitation impact.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-10-27T15:26:14.126Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 6903adccaebfcd54748fc906

Added to database: 10/30/2025, 6:26:20 PM

Last enriched: 10/30/2025, 6:40:49 PM

Last updated: 10/30/2025, 8:45:08 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats