# CVE-2020-3111: Cisco IP Phone Remote Code Execution and Denial of Service Vulnerability > An adjacent attacker can execute arbitrary code with root privileges or cause a denial of service on Cisco IP Phones via crafted CDP packets. - **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 5 Feb 2020 - **Updated:** 15 Nov 2024 - **Also known as:** GHSA-w6xx-2hjv-77cm ## What is CVE-2020-3111? CVE-2020-3111 is a high-severity memory corruption vulnerability in Cisco IP phone, published on 5 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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). Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2020-3111? It affects 33 products. Products: Cisco Ip Conference Phone 7832 Firmware, Cisco Ip Conference Phone 7832 With Multiplatform Firmware, Cisco Ip Conference Phone 8832 Firmware, Cisco Ip Conference Phone 8832 With Multiplatform Firmware, Cisco Ip Phone 6821 Firmware, Cisco Ip Phone 6841 Firmware, Cisco Ip Phone 6851 Firmware, Cisco Ip Phone 6861 Firmware, Cisco Ip Phone 6871 Firmware, Cisco Ip Phone 7811 Firmware, Cisco Ip Phone 7811 With Multiplatform Firmware, Cisco Ip Phone 7821 Firmware, Cisco Ip Phone 7821 With Multiplatform Firmware, Cisco Ip Phone 7841 Firmware, Cisco Ip Phone 7841 With Multiplatform Firmware, Cisco Ip Phone 7861 Firmware, Cisco Ip Phone 7861 With Multiplatform Firmware, Cisco Ip Phone 8811 Firmware, Cisco Ip Phone 8811 With Multiplatform Firmware, Cisco Ip Phone 8841 Firmware and 13 more. ## How do I fix CVE-2020-3111? No fix has been published for CVE-2020-3111 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-3111 being exploited? There is no known exploitation of CVE-2020-3111 in the wild and no public exploit code. ## Other vulnerabilities in Cisco IP phone - [CVE-2019-1635](https://insights.sbomify.com/CVE-2019-1635/): Cisco IP Phone 7800 Series and 8800 Series Session Initiation Protocol XML Denial of Service Vulnerability (high 7.5) - [CVE-2021-1379](https://insights.sbomify.com/CVE-2021-1379/): Memory corruption in Cisco IP Phones with Multiplatform Firmware (medium 6.5) - [CVE-2019-1684](https://insights.sbomify.com/CVE-2019-1684/): Denial of service in Cisco IP Phone 8800 Series Software (medium 6.5) - [CVE-2021-34711](https://insights.sbomify.com/CVE-2021-34711/): Cisco IP Phone Software Arbitrary File Read Vulnerability (medium 5.5) - [CVE-2019-1922](https://insights.sbomify.com/CVE-2019-1922/): Cisco IP Phone 7800 and 8800 Series Session Initiation Protocol Denial of Service Vulnerability (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-3111 and fix it if it is affected. What it is: CVE-2020-3111 is a high-severity memory corruption vulnerability in Cisco IP phone, published on 5 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-3111 in the wild and no public exploit code. Affected product: Cisco IP phone. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-3111/ (Markdown: https://insights.sbomify.com/CVE-2020-3111/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3111 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3111 - OSV: https://osv.dev/vulnerability/CVE-2020-3111 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-3111/ Summaries are generated and may contain mistakes; the official description above is the record.