# CVE-2022-20804: Cisco Unified Communications Products Denial of Service Vulnerability

> An unauthenticated adjacent attacker can cause a kernel panic and denial of service by sending malicious Cisco Discovery Protocol packets to Cisco Unified Communications Manager.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/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:** 21 Apr 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-x87q-gpr2-r7wm

## What is CVE-2022-20804?

CVE-2022-20804 is a medium-severity denial of service vulnerability in Cisco Unified Communications Manager, published on 21 Apr 2022. 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 of Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) could allow an unauthenticated, adjacent attacker to cause a kernel panic on an affected system, resulting in a denial of service (DoS) condition. This vulnerability is due to incorrect processing of certain Cisco Discovery Protocol packets. An attacker could exploit this vulnerability by continuously sending certain Cisco Discovery Protocol packets to an affected device. A successful exploit could allow the attacker to cause a kernel panic on the system that is running the affected software, resulting in a DoS condition.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2022-20804?

It affects 1 product.


Products: Cisco Unified Communications Manager.

## How do I fix CVE-2022-20804?

No fix has been published for CVE-2022-20804 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-20804 being exploited?

There is no known exploitation of CVE-2022-20804 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Unified Communications Manager

- [CVE-2026-20230](https://insights.sbomify.com/CVE-2026-20230/): Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) (high 8.6, exploited in the wild)
- [CVE-2026-20045](https://insights.sbomify.com/CVE-2026-20045/): Cisco Unified Communications Products Code Injection (high 8.2, exploited in the wild)
- [CVE-2025-20309](https://insights.sbomify.com/CVE-2025-20309/): Cisco Unified Communications Manager Static SSH Credentials Vulnerability (critical 10.0)
- [CVE-2011-1643](https://insights.sbomify.com/CVE-2011-1643/): Information disclosure in n/a (critical 10.0)
- [CVE-2024-20253](https://insights.sbomify.com/CVE-2024-20253/): Deserialization in Cisco Packaged Contact Center Enterprise (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20804 and fix it if it is affected.

What it is: CVE-2022-20804 is a medium-severity denial of service vulnerability in Cisco Unified Communications Manager, published on 21 Apr 2022. 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-2022-20804 in the wild and no public exploit code.

Affected product: Cisco Unified Communications Manager. 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-2022-20804/ (Markdown: https://insights.sbomify.com/CVE-2022-20804/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20804
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20804
- OSV: https://osv.dev/vulnerability/CVE-2022-20804

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-20804/
Summaries are generated and may contain mistakes; the official description above is the record.