CVE-2020-3172: Cisco FXOS and NX-OS Software Cisco Discovery Protocol Arbitrary Code Execution and Denial of Service Vulnerability
A vulnerability in the Cisco Discovery Protocol feature of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to execute arbitrary code as root or cause a denial of service (DoS) condition on an affected device. The vulnerability exists because of insufficiently validated Cisco Discovery Protocol packet headers. An attacker could exploit this vulnerability by sending a crafted Cisco Discovery Protocol packet to a Layer 2-adjacent affected device. A successful exploit could allow the attacker to cause a buffer overflow that could allow the attacker to execute arbitrary code as root or cause a DoS condition on the affected device. Note: 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). Note: This vulnerability is different from the following Cisco FXOS and NX-OS Software Cisco Discovery Protocol vulnerabilities that Cisco announced on Feb. 5, 2020: Cisco FXOS, IOS XR, and NX-OS Software Cisco Discovery Protocol Denial of Service Vulnerability and Cisco NX-OS Software Cisco Discovery Protocol Remote Code Execution Vulnerability.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-3172?
CVE-2020-3172 is rated as Critical, allowing unauthorized attackers to execute arbitrary code or cause denial of service.
How do I fix CVE-2020-3172?
To fix CVE-2020-3172, upgrade to the latest Cisco FXOS or NX-OS Software version as specified in the security advisory.
What devices are affected by CVE-2020-3172?
CVE-2020-3172 affects various Cisco FXOS and NX-OS devices, including the Firepower Extensible Operating System and multiple Cisco Nexus models.
Can CVE-2020-3172 be exploited remotely?
No, CVE-2020-3172 requires an adjacent attacker to exploit the vulnerability, meaning they need to be on the same local network.
Is there a workaround for CVE-2020-3172?
Currently, there are no specific workarounds for CVE-2020-3172 other than applying the recommended software updates.