# CVE-2018-0409: Denial of service in TelePresence Video Communication Server (VCS) and Expressway

> An unauthenticated remote attacker can cause a denial of service in Cisco Unified Communications Manager IM&P and TelePresence VCS by sending malicious packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 15 Aug 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-qqxj-4rg7-qpmv

## What is CVE-2018-0409?

CVE-2018-0409 is a high-severity denial of service vulnerability in Cisco Systems, Inc. TelePresence Video Communication Server (VCS) and Expressway, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the XCP Router service of the Cisco Unified Communications Manager IM & Presence Service (CUCM IM&P) and the Cisco TelePresence Video Communication Server (VCS) and Expressway could allow an unauthenticated, remote attacker to cause a temporary service outage for all IM&P users, resulting in a denial of service (DoS) condition. The vulnerability is due to improper validation of user-supplied input. An attacker could exploit this vulnerability by sending a malicious IPv4 or IPv6 packet to an affected device on TCP port 7400. An exploit could allow the attacker to overread a buffer, resulting in a crash and restart of the XCP Router service. Cisco Bug IDs: CSCvg97663, CSCvi55947.

Weakness: CWE-125 (Out-of-bounds Read), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-0409?

It affects 2 products.


Products: Cisco Telepresence Video Communication Server, Cisco Unified Communications Manager Im and Presence Service.

## How do I fix CVE-2018-0409?

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

## Is CVE-2018-0409 being exploited?

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

## Other vulnerabilities in Cisco Systems, Inc. TelePresence Video Communication Server (VCS) and Expressway

- [CVE-2023-20105](https://insights.sbomify.com/CVE-2023-20105/): Privilege escalation in Cisco TelePresence Video Communication Server (VCS) Expressway (critical 9.6)
- [CVE-2023-20192](https://insights.sbomify.com/CVE-2023-20192/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Privilege Escalation Vulnerabilities (critical 9.6)
- [CVE-2022-20754](https://insights.sbomify.com/CVE-2022-20754/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0)
- [CVE-2022-20755](https://insights.sbomify.com/CVE-2022-20755/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0)
- [CVE-2016-1468](https://insights.sbomify.com/CVE-2016-1468/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0409 and fix it if it is affected.

What it is: CVE-2018-0409 is a high-severity denial of service vulnerability in Cisco Systems, Inc. TelePresence Video Communication Server (VCS) and Expressway, published on 15 Aug 2018. 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-2018-0409 in the wild and no public exploit code.

Affected product: Cisco Systems, Inc. TelePresence Video Communication Server (VCS) and Expressway. 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-2018-0409/ (Markdown: https://insights.sbomify.com/CVE-2018-0409/index.md)
```

## Sources

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

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