Skip to content
Fencer Intel
medium 5.9

CVE-2020-27338 json

An issue was discovered in Treck IPv6 before 6.0.1.68.

published 5y ago modified 4mo ago also EUVD-2020-19851

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

An issue was discovered in Treck IPv6 before 6.0.1.68. Improper Input Validation in the DHCPv6 client component allows an unauthenticated remote attacker to cause an Out of Bounds Read, and possibly a Denial of Service via adjacent network access.

Patch / fix

  • treck ipv6 6.0.1.68

Is CVE-2020-27338 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-20-353-01 updated cvss 5.9

Treck TCP/IP Stack (Update A)

  • Treck Inc TCP/IP stack DHCPv6 <= 6.0.1.67 Treck Inc TCP/IP stack HTTP Server <= 6.0.1.67 Treck Inc TCP/IP stack IPv6 <= 6.0.1.67
    affected: mitigation “Treck recommends users apply the latest version of the affected products (Treck TCP/IP 6.0.1.68 or later versions). To obtain patches, email security@treck.com” treck.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

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AC:H/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N
CNA 3.1 5.9 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
NVD 3.1 7.1 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
NVD 2.0 4.8 AV:A/AC:L/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.