CVE-2020-3119
No exploitation reported by the sources we read.
- Published2020-02-05
- Fixed in14.2\(1j\) · 9.3\(2\) · 7.3\(6\)n1\(1\) · 7.0\(3\)i7\(8\)
- WeaknessCWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability in the Cisco Discovery Protocol implementation for Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to execute arbitrary code or cause a reload on an affected device. The vulnerability exists because the Cisco Discovery Protocol parser does not properly validate input for certain fields in a Cisco Discovery Protocol message. An attacker could exploit this vulnerability by sending a malicious Cisco Discovery Protocol packet to an affected device. An successful exploit could allow the attacker to cause a stack overflow, which could allow the attacker to execute arbitrary code with administrative privileges on an affected device. Cisco Discovery Protocol is a Layer 2 protocol. To exploit this vulnerability, an attacker must be in the same broadcast domain as the affected device (Layer 2 adjacent).
Timeline
dates in UTC- 2020-02-0518:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-3119?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-3119?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 14.x | ≥ 14.0, < 14.2\(1j\) | 14.2\(1j\) | NVD |
| 9.3 | ≥ 7.0\(3\)f2, < 9.3\(2\) | 9.3\(2\) | NVD |
| 9.3 | < 9.3\(2\) | 9.3\(2\) | NVD |
| 7.x | ≥ 7.1, < 7.3\(6\)n1\(1\) | 7.3\(6\)n1\(1\) | NVD |
| 7.0 | ≥ 7.0\(3\)i, < 7.0\(3\)i7\(8\) | 7.0\(3\)i7\(8\) | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | ≥ 4.0, < 4.0\(4f\) | 4.0\(4f\) | NVD |
| 3.2 | < 3.2\(3m\) | 3.2\(3m\) | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Cisco nx-os to 14.2\(1j\) · 9.3\(2\) · 7.3\(6\)n1\(1\) · 7.0\(3\)i7\(8\)
Advisories and patches
- tools.cisco.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-02-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-3119?
Is CVE-2020-3119 actively exploited?
What is the CVSS score for CVE-2020-3119?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.