dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Mar 2022.
Tcp\/ipApplication · Treck

CVE-2020-11899

MEDIUM · 5.4 CVSS v3.1 Published 2020-06-17
Fix available
A fix is available. Upgrade to 6.0.1.66 or later.
See remediation →
99/100
Remediation priority · Urgent
In the wild Public exploit No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Treck TCP/IP stack before version 6.0.1.66 contains an out-of-bounds read vulnerability in its IPv6 packet processing code. This memory safety flaw allows reading beyond the boundaries of an allocated buffer when handling malformed or crafted IPv6 packets, potentially leading to information disclosure or undefined behavior.

MitigationUpgrade the Treck TCP/IP stack to version 6.0.1.66 or later. If upgrading is not immediately feasible, implement network-level filtering to reject malformed IPv6 packets before they reach the affected system.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tcp\/ipApplication
Affected:< 6.0.1.66
Wyse 5050 All In One FirmwareOperating system
Affected:all versions
Wyse 7030 FirmwareOperating system
Affected:all versions
Wyse 5030 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Treck TCP/IP stack is in use
    Search for Treck library files (typically named 'treck.lib', 'libtreck.a', or 'treck.dll') on the system, or check embedded device firmware components for references to Treck TCP/IP
    Affected if Treck TCP/IP stack is present in the environment
  2. Determine Treck TCP/IP stack version
    If Treck libraries are found, check the file version information or query the stack version through any available management interface, then compare against the fixed version 6.0.1.66
    Affected if Installed version is earlier than 6.0.1.66
  3. Identify Dell Wyse device models
    Check system information, BIOS/UEFI, or device label to determine if the system is a Dell Wyse 5050, 5030, or 7030 all-in-one terminal
    Affected if Device is a Dell Wyse 5050, 5030, or 7030 (all firmware versions are affected)
  4. Verify IPv6 processing is enabled
    Check network stack configuration or device settings to determine if IPv6 packet processing is active; for Dell Wyse devices, check the network or firmware settings for IPv6 support
    Affected if IPv6 is enabled and the system processes incoming IPv6 traffic (the vulnerability triggers when handling malformed IPv6 packets)

A user is affected if their environment uses the Treck TCP/IP stack version earlier than 6.0.1.66, or if it is a Dell Wyse 5050, 5030, or 7030 device with IPv6 packet processing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.1.66 or later
Fixed in 6.0.1.66
Interim mitigation

Upgrade the Treck TCP/IP stack to version 6.0.1.66 or later. If upgrading is not immediately feasible, implement network-level filtering to reject malformed IPv6 packets before they reach the affected system.

Recommended fix High confidence

Treck TCP/IP 6.0.1.66 (or later)

  1. Identify the Treck TCP/IP stack version currently in use
  2. For Wyse 5050, 7030, and 5030 devices: Contact Dell support or check Dell's support website for available firmware updates that address CVE-2020-11899
  3. If using Treck TCP/IP directly in other products: Upgrade to Treck TCP/IP version 6.0.1.66 or later which contains the fix for the IPv6 out-of-bounds read vulnerability
  4. After upgrade, verify the new Treck version is 6.0.1.66 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tcp\/ip Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11899 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data