CVE-2025-29911
📋 TL;DR
A critical heap buffer overflow vulnerability in CryptoLib versions 1.3.3 and prior allows attackers to cause denial of service or potentially execute arbitrary code by sending maliciously crafted AOS frames. This affects spacecraft communications secured with the SDLS-EP protocol using vulnerable CryptoLib implementations. Systems using cFS with CryptoLib for space-ground communications are at risk.
💻 Affected Systems
- NASA CryptoLib
📦 What is this software?
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Remote code execution leading to complete compromise of spacecraft communications, potential command injection, or permanent system disruption.
Likely Case
Denial of service causing communication disruption between spacecraft and ground stations, potentially requiring system restart.
If Mitigated
Controlled crash or system restart without data loss if proper segmentation and monitoring are in place.
🎯 Exploit Status
Exploitation requires crafting malicious AOS frames but no authentication is needed. Space communication protocols may add complexity.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Not available
Vendor Advisory: https://github.com/nasa/CryptoLib/security/advisories/GHSA-7g6g-9gj4-8c68
Restart Required: Yes
Instructions:
1. Monitor GitHub repository for patches. 2. Apply patch when available. 3. Restart affected cFS applications. 4. Validate communications post-patch.
🔧 Temporary Workarounds
Input Validation Enhancement
allAdd length validation before accessing FECF fields in Crypto_AOS_ProcessSecurity function
// Code modification required: Add check: if (len_ingest < current_managed_parameters_struct.max_frame_size) return error;
Network Segmentation
allIsolate ground station networks from untrusted networks
firewall rules to restrict access to ground station interfaces
🧯 If You Can't Patch
- Implement network monitoring for anomalous AOS frame patterns
- Deploy application-level firewalls to filter malformed SDLS-EP traffic
🔍 How to Verify
Check if Vulnerable:
Check CryptoLib version in use and verify if AOS frame processing is enabledCheck Version:
Check build configuration or source code for CryptoLib version markersVerify Fix Applied:
Test with crafted AOS frames of insufficient length to verify no buffer overflow occurs📡 Detection & Monitoring
Log Indicators:
- Application crashes in cFS
- Memory access violation logs
- Unexpected restarts of CryptoLib processes
Network Indicators:
- AOS frames with abnormal length fields
- SDLS-EP traffic with malformed FECF
SIEM Query:
search 'Crypto_AOS_ProcessSecurity' AND (crash OR overflow OR exception)