Threats / Treck TCP/IP stack / CVE-2020-11899
CVE-2020-11899
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Treck TCP/IP stack IPv6 vulnerability
The Treck TCP/IP stack contains an out-of-bounds read vulnerability in IPv6 processing that enables information disclosure.
Verdict
Today item — known-exploited.
An out-of-bounds read in IPv6 handling allows attackers to read adjacent memory regions, potentially exposing sensitive data. The vulnerability has been exploited in the wild but does not directly enable code execution or system compromise without chaining.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
Probability (EPSS)
EPSS 0.1842 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Treck TCP/IP stack, IPv6. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-125 Out-of-bounds Read — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malformed IPv6 packet to trigger an out-of-bounds read in the Treck stack.
Business
Sensitive data in adjacent memory regions becomes accessible to the attacker, risking credential or configuration exposure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract information from the leaked memory to identify system state, running services, or authentication tokens.
Business
Attackers gain reconnaissance data that enables lateral movement or privilege escalation in subsequent attacks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05