CVE-2017-12249
No exploitation reported by the sources we read.
- Published2017-09-13
- WeaknessCWE-16 · CWE-668
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2017-09-1322:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-12249?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-12249?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | ≤ 2.0.15 | no fix published | NVD |
| 2.1 | = 2.1.0 | no fix published | NVD |
| 2.1 | = 2.1.1 | no fix published | NVD |
| 2.1 | = 2.1.2 | no fix published | NVD |
| 2.1 | = 2.1.3 | no fix published | NVD |
| 2.1 | = 2.1.4 | no fix published | NVD |
| 2.1 | = 2.1.5 | no fix published | NVD |
| 2.1 | = 2.1.6 | no fix published | NVD |
| 2.1 | = 2.1.7 | no fix published | NVD |
| 2.1 | = 2.1.8 | no fix published | NVD |
| 2.1 | = 2.1.9 | no fix published | NVD |
| 2.1 | = 2.1.10 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- tools.cisco.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.1read 2026-10-23
- NVDCVSS 2.09read 2026-10-23
- CNAweakness (CWE)CWE-16read 2026-10-23
- NVDweakness (CWE)CWE-668read 2026-10-23
- FIRST EPSSEPSS score3.1 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- Published
- 2017-09-13
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-12249?
Is CVE-2017-12249 actively exploited?
What is the CVSS score for CVE-2017-12249?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.