Meeting ServerApplication · Cisco

CVE-2017-12264

MEDIUM · 5.3 CVSS v3.0 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in the Web Admin Interface of Cisco Meeting Server could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to insufficient bound checks performed by the affected software. An attacker could exploit this vulnerability by sending a malicious HTTP packet to the affected system. A successful exploit could allow the attacker to cause a reload of the Web Admin Server. Cisco Bug IDs: CSCve89149.

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 confidence

A denial of service vulnerability in the Cisco Meeting Server Web Admin Interface allows unauthenticated remote attackers to send malicious HTTP packets that trigger insufficient bound checks, causing the Web Admin Server to reload. The vulnerability requires no authentication and is exploited via specially crafted HTTP requests.

MitigationApply the Cisco patch for bug CSCve89149. As an interim measure, restrict network access to the Web Admin Interface to trusted IP addresses or networks to reduce attack surface.

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
Affected:all versions

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco Meeting Server is deployed
    Identify if Cisco Meeting Server software is running on the system. Check for CMS-related processes such as callbridge, webadmin, or the cms command-line tool. On the server, run 'ps aux | grep -i cms' or list installed packages.
    Affected if Cisco Meeting Server is installed and running on the system
  2. Verify Web Admin Interface is enabled
    Determine if the Web Admin service is active and listening for connections. Use netstat or ss to check if port 443, 8443, or the configured admin port is in LISTEN state, for example: 'ss -tlnp | grep -E "(443|8443)"' or check the CMS configuration.
    Affected if Web Admin Interface is enabled and listening on a network port
  3. Assess network exposure of Web Admin Interface
    Review firewall rules, network ACLs, or cloud security group configurations to determine if the Web Admin port is open to untrusted IP addresses or broad network ranges. Check for rules allowing traffic from 0.0.0.0/0 or non-internal subnets.
    Affected if Web Admin Interface is reachable from untrusted or public IP addresses
  4. Look for evidence of service restarts
    Review system logs and Web Admin service logs for unplanned reloads or crashes. Check timestamps for sudden Web Admin restarts that were not initiated by administrators.
    Affected if Unexplained Web Admin service reloads are occurring

A system is vulnerable if Cisco Meeting Server is running with the Web Admin Interface enabled and exposed to untrusted network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch for bug CSCve89149. As an interim measure, restrict network access to the Web Admin Interface to trusted IP addresses or networks to reduce attack surface.

Fix this in Meeting Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12264 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12264 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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