# CVE-2020-11896: Memory corruption in n/a

> A memory corruption vulnerability in the Treck TCP/IP stack allows remote attackers to execute arbitrary code via IPv4 tunneling.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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:** 17 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hwgx-cxhm-g3q3

## What is CVE-2020-11896?

CVE-2020-11896 is a critical memory corruption vulnerability in n/a, published on 17 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2020-11896?

It affects 1 product.


Products: Treck Tcp\/Ip.

## How do I fix CVE-2020-11896?

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

## Is CVE-2020-11896 being exploited?

There is no known exploitation of CVE-2020-11896 in the wild and no public exploit code.

Public exploit code:

- PoC for CVE-2020-11896 Treck TCP/IP stack and device asset investigation (github_poc): https://github.com/Fans0n-Fan/Treck20-Related
- RCE exploit for CVE-2020-11896 (Ripple20 IP-in-IP Heap Overflow Vulnerability) targeting Digi Connect ME 9210 (github_poc): https://github.com/0xkol/ripple20-digi-connect-exploit

## Other vulnerabilities in n/a

- [CVE-2020-25066](https://insights.sbomify.com/CVE-2020-25066/): Memory corruption in n/a (critical 10.0)
- [CVE-2020-11897](https://insights.sbomify.com/CVE-2020-11897/): Memory corruption in n/a (critical 10.0)
- [CVE-2020-11910](https://insights.sbomify.com/CVE-2020-11910/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11898](https://insights.sbomify.com/CVE-2020-11898/): Information disclosure in n/a (critical 9.1)
- [CVE-2020-11909](https://insights.sbomify.com/CVE-2020-11909/): The Treck TCP/IP stack before 6.0.1.66 has an IPv4 Integer Underflow. (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11896 and fix it if it is affected.

What it is: CVE-2020-11896 is a critical memory corruption vulnerability in n/a, published on 17 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11896 in the wild and no public exploit code.

Affected product: n/a. 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-2020-11896/ (Markdown: https://insights.sbomify.com/CVE-2020-11896/index.md)
```

## Sources

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

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