# CVE-2017-6794: Command injection in Cisco Meeting Server

> Authenticated local attackers can inject commands via the CLI to escalate privileges to root on Cisco Meeting Server.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6929-fmg8-wwgh

## What is CVE-2017-6794?

CVE-2017-6794 is a medium-severity command injection vulnerability in Cisco Meeting Server, published on 7 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the CLI command-parsing code of Cisco Meeting Server could allow an authenticated, local attacker to perform command injection and escalate their privileges to root. The attacker must first authenticate to the application with valid administrator credentials. The vulnerability is due to insufficient validation of user-supplied input at the CLI for certain commands. An attacker could exploit this vulnerability by authenticating to the affected application and submitting a crafted CLI command for execution at the Cisco Meeting Server CLI. An exploit could allow the attacker to perform command injection and escalate their privilege level to root. Vulnerable Products: This vulnerability exists in Cisco Meeting Server software versions prior to and including 2.0, 2.1, and 2.2. Cisco Bug IDs: CSCvf53830.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Meeting Server.

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

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

## Is CVE-2017-6794 being exploited?

There is no known exploitation of CVE-2017-6794 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-6794 and fix it if it is affected.

What it is: CVE-2017-6794 is a medium-severity command injection vulnerability in Cisco Meeting Server, published on 7 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6794 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-6794/ (Markdown: https://insights.sbomify.com/CVE-2017-6794/index.md)
```

## Sources

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

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