# CVE-2020-11899: Treck TCP/IP stack Out-of-Bounds Read

> An out-of-bounds read in the Treck TCP/IP stack allows attackers to cause denial of service or disclose sensitive information via IPv6 packets.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6r3w-c7h6-wfhg

## What is CVE-2020-11899?

CVE-2020-11899 is a medium-severity memory corruption vulnerability in n/a, published on 17 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 4 products.


Products: Dell Wyse 5030 Firmware, Dell Wyse 5050 All-in-One Firmware, Dell Wyse 7030 Firmware, Treck Tcp\/Ip.

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

No fix has been published for CVE-2020-11899 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Mar 2022.

## Is CVE-2020-11899 being exploited?

Yes. Attackers have exploited CVE-2020-11899 in the wild since at least 3 Mar 2022.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11899 is a medium-severity memory corruption vulnerability in n/a, published on 17 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-11899 in the wild since at least 3 Mar 2022.

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-11899/ (Markdown: https://insights.sbomify.com/CVE-2020-11899/index.md)
```

## Sources

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

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