Security Advisory

CVE-2020-3162: Cisco IoT FND CoAP Denial of Service

Last updated:
  • CVE-2020-3162

CVE-2020-3162 is an input validation flaw (CWE-20) in the CoAP implementation of Cisco IoT Field Network Director before release 4.6: one malformed CoAP packet from an unauthenticated remote attacker can stop the CoAP server and cut communication to the IoT endpoints. NVD and Cisco score it 7.5. Cisco fixed it in release 4.6.

Vulnerability summary

CVSS base score

7.5

High severity

EPSS score (FIRST)

1.7%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-3162 · Source: NVD

Affected components

ComponentCPEVersion range
Cisco IoT Field Network Director (IoT FND)cpe:2.3:a:cisco:iot_field_network_director:*:*:*:*:*:*:*:*releases earlier than 4.6; fixed in 4.6 and later (Cisco cisco-sa-iot-coap-dos-WTBu6YTq, NVD)

What does this mean for affected devices?

NVD carries Cisco's description: "A vulnerability in the Constrained Application Protocol (CoAP) implementation of Cisco IoT Field Network Director could allow an unauthenticated remote attacker to cause a denial of service (DoS) condition on an affected device." NVD's Primary score is 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, the same vector Cisco gives in CVSS 3.0. Both classify it as CWE-20, improper input validation. The CPE configuration covers IoT Field Network Director before 4.6.0, and the record was published on 2020-04-15 (NVD).

What does an attacker need?

Only network reach to the CoAP service. Cisco says the flaw "is due to insufficient input validation of incoming CoAP traffic" and that "an attacker could exploit this vulnerability by sending a malformed CoAP packet to an affected device." No credentials or user action are needed. The result is that the CoAP server stops, "interrupting communication to the IoT endpoints" that the platform talks to over CoAP. Confidentiality and integrity are not affected; the impact is availability of the management path to the field devices. CISA's SSVC entry on the NVD record, dated 2024-11-15, rates exploitation "none", automatable "yes" and technical impact "partial".

Which version is fixed?

Cisco's advisory cisco-sa-iot-coap-dos-WTBu6YTq, published on 2020-04-15 (version 1.0, Final, Cisco bug CSCvs44179), says the flaw affects IoT Field Network Director "if it is running a software release earlier than Release 4.6" and that Cisco "fixed this vulnerability in Cisco IoT Field Network Director releases 4.6 and later." There are no workarounds. Cisco PSIRT was not aware of public announcements or malicious use, and the bug was found during the resolution of a Cisco TAC support case. The CVE record, assigned by Cisco, carries the same advisory and bug ID.

What should operators do?

Move IoT Field Network Director to 4.6 or later. Until then, the CoAP port is the attack surface: CoAP runs over UDP, so allow it only from the field network segments that need it and keep it off the internet. Our CoAP security guide covers exposure and the security modes, and NIST SP 800-40 patch management covers how to schedule the upgrade. Other CoAP stack flaws include CVE-2024-0962 and CVE-2025-34468 in libcoap and CVE-2022-39368, a DTLS throttling bug in Eclipse Californium that also ends in dropped traffic.

CVE-2020-3162 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.01707, the 77.7th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: CoAP implementation of Cisco IoT FND, malformed CoAP packet forces CoAP server to stop; [email protected] Primary CVSS 3.1 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; [email protected] CVSS 3.0 7.5 same vector; CWE-20; CPE iot_field_network_director < 4.6.0; published 2020-04-15; CISA ADP SSVC 2024-11-15 exploitation none, automatable yes, technical impact partial. — NVD
  • Cisco cisco-sa-iot-coap-dos-WTBu6YTq, first published 2020-04-15, version 1.0 Final, bug CSCvs44179: affects IoT FND releases earlier than 4.6; fixed in 4.6 and later; no workarounds; PSIRT not aware of public announcements or malicious use; found during resolution of a TAC support case. — Cisco Security Advisory
  • CVE record assigned by Cisco: product Cisco IoT Field Network Director (IoT-FND), advisory cisco-sa-iot-coap-dos-WTBu6YTq, defect CSCvs44179. — CVE.org
  • Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.01707, percentile 0.77719, dataset 2026-11-17, read 2026-11-18. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Cisco Security Advisory cisco-sa-iot-coap-dos-WTBu6YTq: Cisco IoT Field Network Director CoAP Denial of Service
  3. CVE.org record CVE-2020-3162
  4. CISA KEV
  5. FIRST EPSS

Frequently asked questions

Which IoT Field Network Director release fixes CVE-2020-3162?

Release 4.6 and later. Cisco says every release earlier than 4.6 is affected and that there are no workarounds (per Cisco advisory cisco-sa-iot-coap-dos-WTBu6YTq and NVD).

Does an attacker need credentials to exploit CVE-2020-3162?

No. Cisco describes an unauthenticated remote attacker who sends a malformed CoAP packet to the device. The CoAP server stops, which interrupts communication to the IoT endpoints; data is neither read nor changed (per Cisco and NVD, vector AV:N/PR:N/C:N/I:N/A:H).

How can operators reduce exposure before upgrading?

Cisco lists no workaround, so the upgrade to 4.6 is the fix. Limiting which networks can reach the CoAP service over UDP narrows who can send the malformed packet, but it does not remove the flaw (per Cisco cisco-sa-iot-coap-dos-WTBu6YTq).

Is CVE-2020-3162 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17), and Cisco PSIRT reported no known malicious use. FIRST EPSS gives it 0.01707, the 77.7th percentile, in the 2026-11-17 dataset (per CISA KEV, Cisco and FIRST EPSS).