CVE-2017-12249 Misconfiguration in Cisco Meeting Server

Critical 9.1 Published Updated

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

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

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, CWE-16

Which versions are affected by CVE-2017-12249?

It affects 1 product.

Products include 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.

Sources

Also known as GHSA-9m39-hmv3-2f6w.

Is CVE-2017-12249 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free