# CVE-2025-29911: CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function

> Heap buffer overflow in CryptoLib allows attackers to cause denial of service or execute arbitrary code via malicious AOS frames.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-7g6g-9gj4-8c68

## What is CVE-2025-29911?

CVE-2025-29911 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 17 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. A critical heap buffer overflow vulnerability was identified in the `Crypto_AOS_ProcessSecurity` function of CryptoLib versions 1.3.3 and prior. This vulnerability allows an attacker to trigger a Denial of Service (DoS) or potentially execute arbitrary code (RCE) by providing a maliciously crafted AOS frame with an insufficient length. The vulnerability lies in the function `Crypto_AOS_ProcessSecurity`, specifically during the processing of the Frame Error Control Field (FECF). The affected code attempts to read from the `p_ingest` buffer at indices `current_managed_parameters_struct.max_frame_size - 2` and `current_managed_parameters_struct.max_frame_size - 1` without verifying if `len_ingest` is sufficiently large. This leads to a heap buffer overflow when `len_ingest` is smaller than `max_frame_size`. As of time of publication, no known patched versions exist.

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

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

It affects 1 product.


Products: Nasa Cryptolib.

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

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

## Is CVE-2025-29911 being exploited?

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

## Other vulnerabilities in nasa CryptoLib

- [CVE-2025-30216](https://insights.sbomify.com/CVE-2025-30216/): CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length (critical 9.4)
- [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-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-29911 and fix it if it is affected.

What it is: CVE-2025-29911 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 17 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-29911 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-29911/ (Markdown: https://insights.sbomify.com/CVE-2025-29911/index.md)
```

## Sources

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

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