Denial of service via unreleased counter buffer
Published Mar 17, 2025 · Updated Mar 18, 2025
Memory leak in NASA CryptoLib 1.3.3 and earlier allows remote attackers to exhaust memory via crafted telecommand frames. The crypto_handle_incrementing_nontransmitted_counter function allocates temp_counter but guards free(temp_counter) with if (!temp_counter), leaving every successful allocation unreleased. Repeated processing in long-running or high-throughput deployments degrades performance and can interrupt the service through memory exhaustion.
Summary
What happened
Memory leak in NASA CryptoLib 1.3.3 and earlier allows remote attackers to exhaust memory via crafted telecommand frames. The crypto_handle_incrementing_nontransmitted_counter function allocates temp_counter but guards free(temp_counter) with if (!temp_counter), leaving every successful allocation unreleased. Repeated processing in long-running or high-throughput deployments degrades performance and can interrupt the service through memory exhaustion.
The record
- CVE
- CVE-2025-29910
- Published
- Mar 17, 2025
- Updated
- Mar 18, 2025
- Vendor
- NASA
- Product
- CryptoLib
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2025CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory AddressSanitizer proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo