CVE-2020-3111

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 3.1% (87th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2020 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The CVE record's CNA (Cisco Systems, Inc.) lists Cisco IP phone versions before 12.7(1) as affected. No release containing a fix is confirmed on record.

A vulnerability in the Cisco Discovery Protocol implementation for the Cisco IP Phone could allow an unauthenticated, adjacent attacker to remotely execute code with root privileges or cause a reload of an affected IP phone. The vulnerability is due to missing checks when processing Cisco Discovery Protocol messages. An attacker could exploit this vulnerability by sending a crafted Cisco Discovery Protocol packet to the targeted IP phone. A successful exploit could allow the attacker to remotely execute code with root privileges or cause a reload of an affected IP phone, resulting in a denial of service (DoS) condition. 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).

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation3.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2020. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.
EPSS PROB
3.1%
EPSS %ILE
87th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2020. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 5, 2020

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 9, 2026
No fix on record since 2020.
Web page

Cisco IP Phone Remote Code Execution and Denial of Service Vulnerability

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-voip-phones-rce-dos
Web page

Locked Out | Packet Storm

http://packetstormsecurity.com/files/156203/Cisco-Discovery-Protocol-CDP-Remote-Device-Takeover.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 150 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 62 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:27 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  2. 2026-10-14 16:28 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  3. 2026-10-13 16:28 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  4. 2026-10-12 19:37 UTCEG score recompute
  5. 2026-10-12 16:29 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  6. 2026-10-12 00:00 UTCEG score recompute
  7. 2026-10-11 13:43 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  8. 2026-10-10 19:56 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  9. 2026-10-09 20:04 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  10. 2026-10-08 16:38 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  11. 2026-10-07 23:44 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  12. 2026-10-06 15:13 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  13. 2026-10-05 17:39 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  14. 2026-10-03 14:22 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  15. 2026-09-30 15:18 UTCEG score recompute
  16. 2026-09-30 14:59 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  17. 2026-09-29 15:14 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  18. 2026-09-27 13:41 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  19. 2026-09-26 15:54 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  20. 2026-09-24 14:00 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  21. 2026-09-22 14:43 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  22. 2026-09-21 20:28 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  23. 2026-09-20 20:11 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  24. 2026-09-19 15:37 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  25. 2026-09-18 19:23 UTCEPSS rescoreEPSS 3.1% · 87th percentile
Show 63 more
  1. 2026-09-17 19:22 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  2. 2026-09-16 14:04 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  3. 2026-09-15 03:06 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  4. 2026-09-13 16:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  5. 2026-09-12 14:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  6. 2026-09-11 09:32 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  7. 2026-09-08 21:56 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  8. 2026-09-07 15:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  9. 2026-09-06 13:44 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  10. 2026-09-05 15:24 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  11. 2026-09-04 13:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  12. 2026-09-04 05:03 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  13. 2026-09-02 14:08 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  14. 2026-09-01 03:32 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  15. 2026-08-30 19:14 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  16. 2026-08-30 01:18 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  17. 2026-08-27 14:21 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  18. 2026-08-26 14:42 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  19. 2026-08-25 13:45 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  20. 2026-08-21 23:45 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  21. 2026-08-20 22:52 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  22. 2026-08-19 17:00 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  23. 2026-08-18 13:44 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  24. 2026-08-17 13:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  25. 2026-08-16 14:52 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  26. 2026-08-16 02:11 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  27. 2026-08-15 01:26 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  28. 2026-08-13 21:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  29. 2026-08-12 13:47 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  30. 2026-08-09 13:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  31. 2026-08-08 16:33 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  32. 2026-08-07 16:23 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  33. 2026-08-06 13:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  34. 2026-08-04 15:06 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  35. 2026-08-04 10:34 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  36. 2026-08-02 02:23 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  37. 2026-08-01 04:12 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  38. 2026-07-30 16:25 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  39. 2026-07-30 01:27 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  40. 2026-07-28 15:33 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  41. 2026-07-26 14:51 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  42. 2026-07-25 14:15 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  43. 2026-07-24 14:14 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  44. 2026-07-23 14:15 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  45. 2026-07-23 01:52 UTCEG score recompute
  46. 2026-07-22 22:39 UTCEG score recompute
  47. 2026-07-22 14:05 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  48. 2026-07-21 15:22 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  49. 2026-07-20 17:04 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  50. 2026-07-19 14:28 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  51. 2026-07-19 02:26 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  52. 2026-07-16 16:59 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  53. 2026-07-15 16:55 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  54. 2026-07-15 01:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  55. 2026-07-13 22:27 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  56. 2026-07-13 06:10 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  57. 2026-07-12 05:44 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  58. 2026-07-11 08:25 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  59. 2026-07-09 19:07 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  60. 2026-07-08 15:12 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  61. 2026-07-07 13:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  62. 2026-07-06 16:25 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  63. 2026-07-06 02:21 UTCEPSS rescoreEPSS 3.1% · 86th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-3111?
CVE-2020-3111 is a high-severity vulnerability; its CVE record was published on February 5, 2020. A vulnerability in the Cisco Discovery Protocol implementation for the Cisco IP Phone could allow an unauthenticated, adjacent attacker to remotely execute code with root privileges or cause a reload of an affected IP phone. The vulnerability is due to missing checks when processing Cisco Discovery…
When was CVE-2020-3111 made public?
CVE-2020-3111 was made public on February 5, 2020: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on February 5, 2020. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2020-3111 actively exploited?
CVE-2020-3111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-3111?
CVE-2020-3111 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-3111?
No fix for CVE-2020-3111 has been recorded since its CVE record was published in 2020. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix. The CVE record's CNA (Cisco Systems, Inc.) lists Cisco IP phone versions before 12.7(1) as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-3111

Explore →

Is Your Infrastructure Affected by CVE-2020-3111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs