Skip to content
Fencer Intel
high 7.5

CVE-2020-24337 json

An issue was discovered in picoTCP and picoTCP-NG through 1.7.0.

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

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

Summary

An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. When an unsupported TCP option with zero length is provided in an incoming TCP packet, it is possible to cause a Denial-of-Service by achieving an infinite loop in the code that parses TCP options, aka tcp_parse_options() in pico_tcp.c.

Is CVE-2020-24337 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 7.5

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

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

CVSS scores

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

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

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.