# CVE-2017-3792: Memory corruption in Cisco TelePresence Multipoint Control Unit (MCU) software version 4.3(1.68) or later configured for Passthrough content mode

> Remote attackers can execute arbitrary code or cause denial of service via crafted IPv4/IPv6 fragments in Passthrough mode.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9fw8-cmw4-jgmg

## What is CVE-2017-3792?

CVE-2017-3792 is a critical memory corruption vulnerability in Cisco TelePresence Multipoint Control Unit (MCU) software version 4.3(1.68) or later configured for Passthrough content mode, published on 1 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in a proprietary device driver in the kernel of Cisco TelePresence Multipoint Control Unit (MCU) Software could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition. The vulnerability is due to improper size validation when reassembling fragmented IPv4 or IPv6 packets. An attacker could exploit this vulnerability by sending crafted IPv4 or IPv6 fragments to a port receiving content in Passthrough content mode. An exploit could allow the attacker to overflow a buffer. If successful, the attacker could execute arbitrary code or cause a DoS condition on the affected system. Cisco TelePresence MCU platforms TelePresence MCU 5300 Series, TelePresence MCU MSE 8510 and TelePresence MCU 4500 are affected when running software version 4.3(1.68) or later configured for Passthrough content mode. Cisco has released software updates that address this vulnerability. Workarounds that address this vulnerability are not available, but mitigations are available. Cisco Bug IDs: CSCuu67675.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Telepresence Mcu Software.

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

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

## Is CVE-2017-3792 being exploited?

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

## Other vulnerabilities in Cisco TelePresence Multipoint Control Unit (MCU) software version 4.3(1.68) or later configured for Passthrough content mode

- [CVE-2014-3397](https://insights.sbomify.com/CVE-2014-3397/): Denial of service in n/a (high 7.8)
- [CVE-2015-4257](https://insights.sbomify.com/CVE-2015-4257/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3792 is a critical memory corruption vulnerability in Cisco TelePresence Multipoint Control Unit (MCU) software version 4.3(1.68) or later configured for Passthrough content mode, published on 1 Feb 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-3792 in the wild and no public exploit code.

Affected product: Cisco TelePresence Multipoint Control Unit (MCU) software version 4.3(1.68) or later configured for Passthrough content mode. 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-3792/ (Markdown: https://insights.sbomify.com/CVE-2017-3792/index.md)
```

## Sources

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

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