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-2026-21900: CWE-125: Out-of-bounds Read in nasa CryptoLib

0
High
VulnerabilityCVE-2026-21900cvecve-2026-21900cwe-125
Published: Sat Jan 10 2026 (01/10/2026, 00:14:33 UTC)
Source: CVE Database V5
Vendor/Project: nasa
Product: CryptoLib

Description

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 version 1.4.3, an out-of-bounds heap read vulnerability in cryptography_encrypt() occurs when parsing JSON metadata from KMC server responses. The flawed strtok iteration pattern uses ptr + strlen(ptr) + 1 which reads one byte past allocated buffer boundaries when processing short or malformed metadata strings. This issue has been patched in version 1.4.3.

AI-Powered Analysis

AILast updated: 01/17/2026, 07:45:50 UTC

Technical Analysis

CVE-2026-21900 is an out-of-bounds heap read vulnerability classified under CWE-125 found in NASA's CryptoLib, a software-only implementation of the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP). This library secures communications between spacecraft running the core Flight System (cFS) and ground stations. The vulnerability exists in the cryptography_encrypt() function when it parses JSON metadata received from Key Management Center (KMC) server responses. Specifically, the issue stems from a flawed use of the strtok function for iterating over strings, where the pointer arithmetic ptr + strlen(ptr) + 1 causes the code to read one byte beyond the allocated buffer boundary when processing short or malformed metadata strings. This out-of-bounds read can lead to undefined behavior, including potential leakage of sensitive memory contents or application crashes. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The flaw was identified and patched in CryptoLib version 1.4.3. While no known exploits have been reported in the wild, the vulnerability's CVSS 4.0 score of 8.2 reflects its high severity due to the potential impact on confidentiality and availability. This vulnerability is particularly relevant to organizations using CryptoLib in space communication systems or related aerospace applications.

Potential Impact

For European organizations, especially those involved in aerospace, satellite communications, or space research, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of sensitive cryptographic material or metadata, potentially compromising the confidentiality of spacecraft-to-ground communications. Additionally, out-of-bounds reads can cause application instability or crashes, impacting the availability of critical communication systems. Given the reliance on secure data links in space missions, any disruption or data leakage could have severe operational and reputational consequences. Although no active exploits are known, the ease of remote exploitation without authentication increases the threat level. Organizations that integrate CryptoLib or similar CCSDS SDLS-EP implementations in their systems must consider this vulnerability a priority for remediation to maintain secure and reliable space communication infrastructure.

Mitigation Recommendations

The primary mitigation is to upgrade CryptoLib to version 1.4.3 or later, where the out-of-bounds read issue has been patched. Organizations should conduct a thorough inventory to identify all systems using CryptoLib, especially those involved in spacecraft communication or ground station operations. Beyond upgrading, it is advisable to audit all JSON parsing routines within the software stack for similar unsafe string handling patterns, particularly those using strtok or manual pointer arithmetic. Implementing bounds checking and safer string handling functions can prevent similar vulnerabilities. Network-level protections such as strict filtering of KMC server responses and anomaly detection for malformed metadata can reduce exposure. Additionally, organizations should monitor for any emerging exploit attempts or related threat intelligence. Regular security assessments and code reviews focusing on memory safety in critical communication components are recommended to prevent recurrence.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T17:24:36.931Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6961a1f5ed32c7f018d59bdf

Added to database: 1/10/2026, 12:48:53 AM

Last enriched: 1/17/2026, 7:45:50 AM

Last updated: 2/6/2026, 7:25:19 PM

Views: 51

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats