# CVE-2017-6785: Missing authorization in Unified Communications Manager

> Authenticated attackers can modify other users' configurations due to missing RBAC checks in Cisco Unified Communications Manager.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9r7g-3f6r-pjwx

## What is CVE-2017-6785?

CVE-2017-6785 is a medium-severity missing authorization vulnerability in Cisco Unified Communications Manager, published on 17 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in configuration modification permissions validation for Cisco Unified Communications Manager could allow an authenticated, remote attacker to perform a horizontal privilege escalation where one user can modify another user's configuration. The vulnerability is due to lack of proper Role Based Access Control (RBAC) when certain user configuration changes are requested. An attacker could exploit this vulnerability by sending an authenticated, crafted HTTP request to the targeted application. An exploit could allow the attacker to impact the integrity of the application where one user can modify the configuration of another user's information. Cisco Bug IDs: CSCve27331. Known Affected Releases: 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Unified Communications Manager.

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

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

## Is CVE-2017-6785 being exploited?

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

## Other vulnerabilities in Cisco Unified Communications Manager

- [CVE-2026-20230](https://insights.sbomify.com/CVE-2026-20230/): Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) (high 8.6, exploited in the wild)
- [CVE-2026-20045](https://insights.sbomify.com/CVE-2026-20045/): Cisco Unified Communications Products Code Injection (high 8.2, exploited in the wild)
- [CVE-2025-20309](https://insights.sbomify.com/CVE-2025-20309/): Cisco Unified Communications Manager Static SSH Credentials Vulnerability (critical 10.0)
- [CVE-2011-1643](https://insights.sbomify.com/CVE-2011-1643/): Information disclosure in n/a (critical 10.0)
- [CVE-2024-20253](https://insights.sbomify.com/CVE-2024-20253/): Deserialization in Cisco Packaged Contact Center Enterprise (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6785 is a medium-severity missing authorization vulnerability in Cisco Unified Communications Manager, published on 17 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6785 in the wild and no public exploit code.

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

## Sources

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

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