# CVE-2020-3163: Cisco Unified Contact Center Enterprise Denial of Service Vulnerability

> Unauthenticated remote attackers can cause a denial of service by sending crafted packets to the Live Data server before a legitimate client connects.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-759q-wfqr-9x82

## What is CVE-2020-3163?

CVE-2020-3163 is a medium-severity vulnerability in Cisco Unified Contact Center Enterprise, published on 19 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Live Data server of Cisco Unified Contact Center Enterprise could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability exists because the affected software improperly manages resources when processing inbound Live Data traffic. An attacker could exploit this vulnerability by sending multiple crafted Live Data packets to an affected device. A successful exploit could cause the affected device to run out of buffer resources, which could result in a stack overflow and cause the affected device to reload, resulting in a DoS condition. Note: The Live Data port in Cisco Unified Contact Center Enterprise devices allows only a single TCP connection. To exploit this vulnerability, an attacker would have to send crafted packets to an affected device before a legitimate Live Data client establishes a connection.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2020-3163?

It affects 1 product.


Products: Cisco Unified Contact Center Enterprise.

## How do I fix CVE-2020-3163?

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

## Is CVE-2020-3163 being exploited?

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

## Other vulnerabilities in Cisco Unified Contact Center Enterprise

- [CVE-2007-5539](https://insights.sbomify.com/CVE-2007-5539/): Privilege escalation in n/a (critical 9.0)
- [CVE-2025-20242](https://insights.sbomify.com/CVE-2025-20242/): Missing authorization in Cisco Unified Contact Center Enterprise (medium 6.5)
- [CVE-2016-1439](https://insights.sbomify.com/CVE-2016-1439/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-6626](https://insights.sbomify.com/CVE-2017-6626/): Hardcoded credentials in Cisco Finesse for Cisco Unified Contact Center Enterprise (medium 5.3)
- [CVE-2014-3323](https://insights.sbomify.com/CVE-2014-3323/): Path traversal in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3163 and fix it if it is affected.

What it is: CVE-2020-3163 is a medium-severity vulnerability in Cisco Unified Contact Center Enterprise, published on 19 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3163 in the wild and no public exploit code.

Affected product: Cisco Unified Contact Center Enterprise. 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-3163/ (Markdown: https://insights.sbomify.com/CVE-2020-3163/index.md)
```

## Sources

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

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