Heap corruption via unchecked IV copy
Published Aug 11, 2025 · Updated Aug 11, 2025
Heap buffer overflow in NASA CryptoLib 1.4.0 and earlier allows remote attackers to corrupt heap memory via a crafted telecommand frame. The Crypto_TC_Check_IV_Setup loop copies 12 IV bytes into a 19-byte allocation starting at offset eight without checking remaining capacity, so the final write lands one byte beyond the buffer. No privileges or user interaction are required; undefined behavior can crash the consuming process or enable more severe exploitation.
Summary
What happened
Heap buffer overflow in NASA CryptoLib 1.4.0 and earlier allows remote attackers to corrupt heap memory via a crafted telecommand frame. The Crypto_TC_Check_IV_Setup loop copies 12 IV bytes into a 19-byte allocation starting at offset eight without checking remaining capacity, so the final write lands one byte beyond the buffer. No privileges or user interaction are required; undefined behavior can crash the consuming process or enable more severe exploitation.
The record
- CVE
- CVE-2025-54878
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- NASA
- Product
- CryptoLib
- Classifications
- CWE-122, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 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.4.1
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.
Public exploit references
- Crafted telecommand-frame 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