CVE-2022-20625
MediumWhat is CVE-2022-20625?
A vulnerability in the Cisco Discovery Protocol service of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause the service to restart, resulting in a denial of service (DoS) condition. This vulnerability is due to improper handling of Cisco Discovery Protocol messages that are processed by the Cisco Discovery Protocol service. An attacker could exploit this vulnerability by sending a series of malicious Cisco Discovery Protocol messages to an affected device. A successful exploit could allow the attacker to cause the Cisco Discovery Protocol service to fail and restart. In rare conditions, repeated failures of the process could occur, which could cause the entire device to restart.
CVSS Vector Breakdown
CVSS 3.1Exploitable from an adjacent network (e.g. same LAN, Wi-Fi segment, Bluetooth).
No special conditions required. Exploit can be performed reliably and repeatedly.
No authentication required. Any anonymous user can exploit this vulnerability.
No user interaction required. Exploit runs without any victim action.
Exploiting the vulnerability only affects the vulnerable component itself.
No confidentiality impact. Sensitive data is not exposed.
No integrity impact. Data cannot be modified.
Reduced performance or intermittent outages, but service remains available.
Known Affected Devices
FAQ
CVE-2022-20625 has a CVSS score of 4.3/10, rated as Medium. Review the affected products list and apply vendor patches.
CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2022-20625 scores 4.3/10 (Medium). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.
The list of devices confirmed to be affected by CVE-2022-20625 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.
Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.