# CVE-2017-12249: Misconfiguration in Cisco Meeting Server

> Authenticated attackers can exploit incorrect default TURN server configurations to gain unauthorized access to internal components and sensitive meeting data.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9m39-hmv3-2f6w

## What is CVE-2017-12249?

CVE-2017-12249 is a critical vulnerability in Cisco Meeting Server, published on 13 Sep 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the Traversal Using Relay NAT (TURN) server included with Cisco Meeting Server (CMS) could allow an authenticated, remote attacker to gain unauthenticated or unauthorized access to components of or sensitive information in an affected system. The vulnerability is due to an incorrect default configuration of the TURN server, which could expose internal interfaces and ports on the external interface of an affected system. An attacker could exploit this vulnerability by using a TURN server to perform an unauthorized connection to a Call Bridge, a Web Bridge, or a database cluster in an affected system, depending on the deployment model and CMS services in use. A successful exploit could allow the attacker to gain unauthenticated access to a Call Bridge or database cluster in an affected system or gain unauthorized access to sensitive meeting information in an affected system. To exploit this vulnerability, the attacker must have valid credentials for the TURN server of the affected system. This vulnerability affects Cisco Meeting Server (CMS) deployments that are running a CMS Software release prior to Release 2.0.16, 2.1.11, or 2.2.6. Cisco Bug IDs: CSCvf51127.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-16

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

It affects 1 product.


Products: Cisco Meeting Server.

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

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

## Is CVE-2017-12249 being exploited?

There is no known exploitation of CVE-2017-12249 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-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)
- [CVE-2018-0262](https://insights.sbomify.com/CVE-2018-0262/): Misconfiguration in Cisco Meeting Server (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12249 is a critical vulnerability in Cisco Meeting Server, published on 13 Sep 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12249 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-12249/ (Markdown: https://insights.sbomify.com/CVE-2017-12249/index.md)
```

## Sources

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

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