# CVE-2025-30216: CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length

> A heap overflow in CryptoLib allows attackers to overwrite memory and potentially execute arbitrary code or crash the system via crafted packets.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-v3jc-5j74-hcjv

## What is CVE-2025-30216?

CVE-2025-30216 is a critical memory corruption vulnerability in nasa CryptoLib, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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. In versions 1.3.3 and prior, a Heap Overflow vulnerability occurs in the `Crypto_TM_ProcessSecurity` function (`crypto_tm.c:1735:8`). When processing the Secondary Header Length of a TM protocol packet, if the Secondary Header Length exceeds the packet's total length, a heap overflow is triggered during the memcpy operation that copies packet data into the dynamically allocated buffer `p_new_dec_frame`. This allows an attacker to overwrite adjacent heap memory, potentially leading to arbitrary code execution or system instability. A patch is available at commit 810fd66d592c883125272fef123c3240db2f170f.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-30216?

It affects 1 product.


Products: Nasa Cryptolib.

## How do I fix CVE-2025-30216?

No fix has been published for CVE-2025-30216 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-30216 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30216 exists.

Public exploit code:

- PoC (github_poc): https://github.com/oliviaisntcringe/CVE-2025-30216-PoC

## Other vulnerabilities in nasa CryptoLib

- [CVE-2025-30356](https://insights.sbomify.com/CVE-2025-30356/): Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity` (critical 9.3)
- [CVE-2025-29909](https://insights.sbomify.com/CVE-2025-29909/): CryptoLib's Crypto_TC_ApplySecurity() Has a Heap Buffer Overflow Vulnerability (high 8.9)
- [CVE-2025-29911](https://insights.sbomify.com/CVE-2025-29911/): CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function (high 8.9)
- [CVE-2025-29912](https://insights.sbomify.com/CVE-2025-29912/): CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity (high 8.9)
- [CVE-2025-29913](https://insights.sbomify.com/CVE-2025-29913/): CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30216 and fix it if it is affected.

What it is: CVE-2025-30216 is a critical memory corruption vulnerability in nasa CryptoLib, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30216 exists.

Affected product: nasa CryptoLib. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30216/ (Markdown: https://insights.sbomify.com/CVE-2025-30216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30216
- OSV: https://osv.dev/vulnerability/CVE-2025-30216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30216/
Summaries are generated and may contain mistakes; the official description above is the record.