Meeting ServerApplication · Cisco
CVE-2017-12249
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in the TURN server component of Cisco Meeting Server (CMS) stems from an incorrect default configuration that exposes internal interfaces and ports on the external network interface. An authenticated attacker with valid TURN server credentials can exploit this misconfiguration to gain unauthorized access to Call Bridge, Web Bridge, or database clusters, potentially obtaining sensitive meeting information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Meeting ServerApplication
<= 2.0.15= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4= 2.1.5= 2.1.6= 2.1.7= 2.1.8= 2.1.9= 2.1.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Meeting Server installation and versionRun 'version' command or check the CMS version through the admin interface to determine if the installed version matches <= 2.0.15, 2.1.0 through 2.1.10Affected if The installed version is one of the affected versions listed in the CVE
-
Verify if TURN server component is enabledCheck the CMS configuration for TURN server status using the admin API or configuration files - look for 'turn' or 'turnserver' settingsAffected if TURN server is enabled and running
-
Inspect TURN server network binding configurationReview TURN server configuration for network interface bindings - specifically check whether internal interfaces (Call Bridge, Web Bridge, database ports) are bound to external network interfacesAffected if Internal service ports (Call Bridge, Web Bridge, database) are exposed on the external TURN interface
-
Review TURN server access control settingsExamine TURN server access control lists or firewall rules to determine if internal resources are accessible without proper isolationAffected if TURN server configuration allows access to internal Call Bridge, Web Bridge, or database clusters from external network
You are affected if you run an affected Cisco Meeting Server version (2.0.15 or earlier, or 2.1.0-2.1.10) with TURN server enabled and internal interfaces are exposed on the external network interface.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Cisco Meeting Server to Release 2.0.16, 2.1.11, 2.2.6 or later to remediate the incorrect TURN server default configuration.
Upgrade to CMS 2.0.16, 2.1.11, or 2.2.6 (or later stable release) based on your current version branch
- 1. Identify the current Cisco Meeting Server (CMS) version by running: version show or cms --version
- 2. Review current TURN server configuration to understand the deployment model and exposed interfaces
- 3. Create a full backup of the CMS configuration and data
- 4. Schedule a maintenance window for the upgrade
- 5. For systems currently on CMS <= 2.0.15: Upgrade to version 2.0.16
- 6. For systems currently on CMS 2.1.0-2.1.2: Upgrade to version 2.1.11
- 7. Alternatively, upgrade to version 2.2.6 or later for any supported deployment (recommended if compatible with your deployment model)
- 8. After upgrade, verify the TURN server configuration is correctly binding to internal interfaces only and not exposing them externally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Meeting Server
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12249 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data