# CVE-2017-6763: Denial of service in Cisco Meeting Server

> Unauthenticated remote attackers can cause a denial of service by sending crafted H.264 packets, restarting the media process.

- **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:** 7 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5rrp-wchw-8jv4

## What is CVE-2017-6763?

CVE-2017-6763 is a high-severity denial of service vulnerability in Cisco Meeting Server, published on 7 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the implementation of the H.264 protocol in Cisco Meeting Server (CMS) 2.1.4 could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected system. The vulnerability exists because the affected application does not properly validate Fragmentation Unit (FU-A) protocol packets. An attacker could exploit this vulnerability by sending a crafted H.264 FU-A packet through the affected application. A successful exploit could allow the attacker to cause a DoS condition on the affected system due to an unexpected restart of the CMS media process on the system. Although the CMS platform continues to operate and only the single, affected CMS media process is restarted, a brief interruption of media traffic for certain users could occur. Cisco Bug IDs: CSCve10131.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Meeting Server.

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

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

## Is CVE-2017-6763 being exploited?

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

## Other vulnerabilities in Cisco Meeting Server

- [CVE-2016-6448](https://insights.sbomify.com/CVE-2016-6448/): Memory corruption in Cisco Meeting Server before 2.0.3 and Acano Server before 1.9.5 (critical 9.8)
- [CVE-2017-12249](https://insights.sbomify.com/CVE-2017-12249/): Misconfiguration in Cisco Meeting Server (critical 9.1)
- [CVE-2016-6445](https://insights.sbomify.com/CVE-2016-6445/): Auth bypass in Cisco Meeting Server (CMS) before 2.0.6 and Acano Server before 1.8.18 and 1.9.x before 1.9.6 (critical 9.1)
- [CVE-2018-0439](https://insights.sbomify.com/CVE-2018-0439/): Cisco Meeting Server Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2016-6444](https://insights.sbomify.com/CVE-2016-6444/): Cross-site request forgery in Cisco Meeting Server 1.8, 1.9, 2.0 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6763 is a high-severity denial of service vulnerability in Cisco Meeting Server, published on 7 Aug 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-6763 in the wild and no public exploit code.

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

## Sources

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

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