Skip to content
Fencer Intel
critical 9.8

CVE-2020-27630 json

In Silicon Labs uC/TCP-IP 3.6.0, TCP ISNs are improperly random.

published 3y ago modified 4mo ago also EUVD-2020-20137

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

Summary

In Silicon Labs uC/TCP-IP 3.6.0, TCP ISNs are improperly random.

Is CVE-2020-27630 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-21-042-01 updated cvss 7.5

Multiple Embedded TCP/IP Stacks (Update B)

  • multiple Capital VSTAR multiple CycloneTCP <= 1.9.6 multiple FNET 4.6.3 multiple MPLAB Net <= 3.6.1 multiple NDKTCPIP <= 2.25 multiple Nucleus NET All < 5.2
    +9 more products
    multiple Nucleus ReadyStart for ARM MIPS and PPC < 2012.12 multiple Nucleus Source Code multiple Nut/Net <= 5.1 multiple picoTCP (EOL) <= 1.7.0 multiple picoTCP-NG <= 1.7.0 multiple uC/TCP-IP (EOL) <= 3.6.0 multiple uIP (EOL) <= 1.0 multiple uIP-Contiki-NG <= 4.5 multiple uIP-Contiki-OS (end-of-life [EOL]) <= 3.0
    affected: vendor fix, mitigation “uIP-Contiki-OS (end-of-life [EOL]). See general recommendations below.” github.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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values

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.