Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2020-11910: ICMPv4 Out-of-Bounds Read in Treck TCP/IP Stack

Published Jun 17, 2020 · Updated 25 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS10.9%96th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Treck
IdentifiersCVE-2020-11910CWE-125 · Out-of-bounds Read

CVE-2020-11910 is an out-of-bounds read vulnerability in the ICMPv4 component of the Treck TCP/IP stack before version 6.0.1.66. Improper validation of attacker-supplied ICMPv4 packets can cause the stack to read beyond valid memory boundaries. The vulnerability is part of Ripple20 and affects products embedding the vulnerable stack.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation causes an out-of-bounds memory read, potentially disrupting network processing or device availability. Information disclosure depends on whether the affected implementation exposes the improperly read memory; this is not established for this specific CVE. Remote code execution is likewise not established for CVE-2020-11910.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to affected devices, remove unnecessary internet exposure, and segment industrial and embedded-device networks. Block unused ICMPv4 message types at network boundaries where operationally feasible. Apply suitable IDS/IPS rules to detect or block malformed traffic while awaiting vendor updates.

Remediation

Patch, then assume compromise.

Apply device-manufacturer firmware or software updates that incorporate a corrected Treck stack. Versions before 6.0.1.66 are affected by this CVE; Treck's broader Ripple20 remediation recommendation is to upgrade to version 6.0.1.67 or later. Downstream users should confirm affected products and obtain supported updates from their device vendors.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
TreckTcp Ipapplication
FAQ

Frequently asked questions

Is CVE-2020-11910 exploited in the wild?
Yes. As of Oct 28, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-11910?
Yes. As of Oct 28, 2026, Mallory has reports of a public exploit for CVE-2020-11910.
Is there a patch for CVE-2020-11910?
Apply device-manufacturer firmware or software updates that incorporate a corrected Treck stack. Versions before 6.0.1.66 are affected by this CVE; Treck's broader Ripple20 remediation recommendation is to upgrade to version 6.0.1.67 or later.
What products are affected by CVE-2020-11910?
Treck Tcp Ip.
How severe is CVE-2020-11910?
CVE-2020-11910 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 10.9% (96th percentile) as of Oct 28, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.