# CVE-2017-6641: Denial of service in Cisco Remote Expert Manager

> Unauthenticated remote attackers can cause denial of service by flooding TCP packets, exhausting resources and disabling ports on Cisco Remote Expert Manager.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 22 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p3m3-vvvv-g35w

## What is CVE-2017-6641?

CVE-2017-6641 is a high-severity denial of service vulnerability in Cisco Remote Expert Manager, published on 22 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the TCP connection handling functionality of Cisco Remote Expert Manager Software 11.0.0 could allow an unauthenticated, remote attacker to disable TCP ports and cause a denial of service (DoS) condition on an affected system. The vulnerability is due to a lack of rate-limiting functionality in the TCP Listen application of the affected software. An attacker could exploit this vulnerability by sending a crafted TCP traffic stream in which specific types of TCP packets are flooded to an affected device, for example a TCP packet stream in which the TCP FIN bit is set in all the TCP packets. A successful exploit could allow the attacker to cause certain TCP listening ports on the affected system to stop accepting incoming connections for a period of time or until the affected device is restarted, resulting in a DoS condition. In addition, system resources, such as CPU and memory, could be exhausted during the attack. Cisco Bug IDs: CSCva29806.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-399

## Which versions are affected by CVE-2017-6641?

It affects 1 product.


Products: Cisco Remote Expert Manager.

## How do I fix CVE-2017-6641?

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

## Is CVE-2017-6641 being exploited?

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

## Other vulnerabilities in Cisco Remote Expert Manager

- [CVE-2017-6642](https://insights.sbomify.com/CVE-2017-6642/): Information disclosure in Cisco Remote Expert Manager (medium 5.3)
- [CVE-2017-6643](https://insights.sbomify.com/CVE-2017-6643/): Information disclosure in Cisco Remote Expert Manager (medium 5.3)
- [CVE-2017-6644](https://insights.sbomify.com/CVE-2017-6644/): Information disclosure in Cisco Remote Expert Manager (medium 5.3)
- [CVE-2017-6645](https://insights.sbomify.com/CVE-2017-6645/): Information disclosure in Cisco Remote Expert Manager (medium 5.3)
- [CVE-2017-6646](https://insights.sbomify.com/CVE-2017-6646/): Information disclosure in Cisco Remote Expert Manager (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6641 and fix it if it is affected.

What it is: CVE-2017-6641 is a high-severity denial of service vulnerability in Cisco Remote Expert Manager, published on 22 May 2017. 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-2017-6641 in the wild and no public exploit code.

Affected product: Cisco Remote Expert 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-2017-6641/ (Markdown: https://insights.sbomify.com/CVE-2017-6641/index.md)
```

## Sources

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

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