Skip to content
Fencer Intel
critical 9.1

CVE-2020-17467 json

An issue was discovered in FNET through 4.6.4.

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

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

Summary

An issue was discovered in FNET through 4.6.4. The code for processing the hostname from an LLMNR request doesn't check for '\0' termination. Therefore, the deduced length of the hostname doesn't reflect the correct length of the actual data. This may lead to Information Disclosure in _fnet_llmnr_poll in fnet_llmnr.c during a response to a malicious request of the DNS class IN.

Is CVE-2020-17467 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-343-01 updated cvss 8.2

Multiple Embedded TCP/IP Stacks

  • multiple open source FNET 4.6.3 multiple open source Nut/Net <= 5.1 multiple open source open-iscsi <= 2.1.12 multiple open source picoTCP (EOL) <= 1.7.0 multiple open source picoTCP-NG <= 1.7.0 multiple open source uIP (EOL) <= 1.0
    +2 more products
    multiple open source uIP-Contiki-NG <= 4.5 multiple open source uIP-Contiki-OS (end-of-life [EOL]) <= 3.0
    affected: vendor fix yanzi.dev

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

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

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/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.