# CVE-2018-0358: Denial of service in Cisco TelePresence Video Communication Server unknown

> Unauthenticated remote attackers can cause a denial of service by exhausting file descriptors through high-volume TCP connections on Cisco VCS Expressway.

- **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:** 21 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-hfw2-jvj9-frm4

## What is CVE-2018-0358?

CVE-2018-0358 is a high-severity denial of service vulnerability in Cisco TelePresence Video Communication Server unknown, published on 21 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the file descriptor handling of Cisco TelePresence Video Communication Server (VCS) Expressway could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to exhaustion of file descriptors while processing a high volume of traffic. An attacker could exploit this vulnerability by establishing a high number of concurrent TCP connections to the vulnerable system. An exploit could allow the attacker to cause a restart in a specific process, resulting in a temporary interruption of service. Cisco Bug IDs: CSCvh77056, CSCvh77058, CSCvh95264.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-769 (DEPRECATED: Uncontrolled File Descriptor Consumption)

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

It affects 1 product.


Products: Cisco Telepresence Video Communication Server.

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

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

## Is CVE-2018-0358 being exploited?

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

## Other vulnerabilities in Cisco TelePresence Video Communication Server unknown

- [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-0358 and fix it if it is affected.

What it is: CVE-2018-0358 is a high-severity denial of service vulnerability in Cisco TelePresence Video Communication Server unknown, published on 21 Jun 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-0358 in the wild and no public exploit code.

Affected product: Cisco TelePresence Video Communication Server unknown. 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-0358/ (Markdown: https://insights.sbomify.com/CVE-2018-0358/index.md)
```

## Sources

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

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