dbcve.org
Tcp\/ipApplication · Treck

CVE-2020-11897

CRITICAL · 10.0 CVSS v3.1 Published 2020-06-17
Fix available
A fix is available. Upgrade to 5.0.1.35 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 5.0.1.35 has an Out-of-Bounds Write via multiple malformed IPv6 packets.

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 · high confidence

A critical out-of-bounds write vulnerability exists in the Treck TCP/IP stack versions prior to 5.0.1.35. The vulnerability is triggered by processing multiple malformed IPv6 packets, allowing an attacker to write data outside the intended buffer boundaries. This can lead to memory corruption and potentially allow remote code execution.

MitigationUpdate the Treck TCP/IP stack to version 5.0.1.35 or later. If patching is not immediately feasible, consider network segmentation to limit exposure to untrusted IPv6 traffic and monitor for anomalous packet patterns.

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:< 5.0.1.35

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 Treck TCP/IP stack usage
    Review product documentation, firmware, or software bill of materials (SBOM) to determine if the Treck TCP/IP stack is integrated into your system or device. Look for 'Treck' or 'treck' references in libraries, firmware strings, or embedded software components.
    Affected if Treck TCP/IP stack is present in the environment and the version is unknown or below 5.0.1.35
  2. Determine installed Treck stack version
    If Treck TCP/IP stack is identified, locate the version information in the device firmware, software build artifacts, or vendor documentation. Compare the discovered version against the affected range of versions prior to 5.0.1.35.
    Affected if The installed Treck TCP/IP stack version is below 5.0.1.35 or cannot be verified
  3. Verify IPv6 functionality is enabled
    Check system or device network configuration settings to determine if IPv6 protocol support is active. This may be found in network stack settings, kernel parameters, or device configuration interfaces.
    Affected if IPv6 is enabled and the Treck TCP/IP stack version is vulnerable
  4. Assess network exposure to IPv6 traffic
    Review network segmentation, firewall rules, and access controls to determine if the device or system can receive untrusted or external IPv6 packets.
    Affected if The system is exposed to untrusted IPv6 network traffic and runs a vulnerable Treck TCP/IP stack version

A system is affected if it runs any version of the Treck TCP/IP stack prior to 5.0.1.35 with IPv6 enabled and potential exposure to untrusted IPv6 packets.

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 5.0.1.35 or later
Fixed in 5.0.1.35
Interim mitigation

Update the Treck TCP/IP stack to version 5.0.1.35 or later. If patching is not immediately feasible, consider network segmentation to limit exposure to untrusted IPv6 traffic and monitor for anomalous packet patterns.

Recommended fix High confidence

5.0.1.35

  1. Identify products or systems that incorporate the Treck TCP/IP stack in your environment
  2. Determine the current version of the Treck TCP/IP stack or the embedded product firmware
  3. Upgrade the Treck TCP/IP stack to version 5.0.1.35 or later, or apply vendor-provided patches that address CVE-2020-11897
  4. If using an affected vendor product (Cisco, Dell, Aruba, HP, etc.), apply the vendor-specific security updates or firmware upgrades
  5. Verify the upgrade was successful by checking the version number
  6. Test the updated system to ensure normal operation
Caveat Review vendor release notes for any compatibility notes; minor version upgrades within the same major release typically have no breaking changes

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

Fix this in Tcp\/ip Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11897 — 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-11897 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