Skip to content
Fencer Vulns
medium 6.3

CVE-2020-11907 json

The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP.

published 2020-06-17 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-4244

cvss
6.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP.

Patch / fix

  • treck tcp/ip 6.0.1.66

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-168-01 updated cvss 5.0

Treck TCP/IP (Update I)

  • Treck Inc. Treck Inc TCP/IP IPv4, IPv6, UDP, DNS
    affected: mitigation “Treck recommends users apply the latest version of the affected products:” rockwellautomation.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.96% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • jsof-tech.com https://www.jsof-tech.com/ripple20/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 5.8 AV:A/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.