dbcve.org
Meeting ServerApplication · Cisco

CVE-2018-0262

HIGH · 8.1 CVSS v3.0 Published 2018-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 Cisco Meeting Server could allow an unauthenticated, remote attacker to gain unauthorized access to components of, or sensitive information in, an affected system, leading to Remote Code Execution. The vulnerability is due to incorrect default configuration of the device, which can expose internal interfaces and ports on the external interface of the system. A successful exploit could allow the attacker to gain unauthenticated access to configuration and database files as well as sensitive meeting information on an affected system. Additionally, if the Traversal Using Relay NAT (TURN) service is enabled and utilizing Transport Layer Security (TLS) connections, an attacker could utilize TURN credentials to forward traffic to device daemons, allowing for remote exploitation. This vulnerability affects Cisco Meeting Server (CMS) Acano X-series platforms that are running a CMS Software release prior to 2.2.11. Cisco Bug IDs: CSCvg76469.

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

The vulnerability in Cisco Meeting Server stems from incorrect default configuration that exposes internal interfaces and ports on the external interface. An unauthenticated remote attacker can gain access to configuration files, database files, and sensitive meeting information. If TURN service with TLS is enabled, attackers can exploit TURN credentials to forward traffic to device daemons, enabling remote code execution.

MitigationUpgrade to Cisco Meeting Server software release 2.2.11 or later and review network configuration to ensure internal interfaces are not exposed on external interfaces. Additionally, if TURN service is enabled, audit TURN credentials and TLS configuration.

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:= 1.9= 2.0= 2.1= 2.2= 2.3= 2.4

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

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/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 checks

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

  1. Identify installed Cisco Meeting Server version
    Access the admin web interface (https://<server>/admin) or use the command line 'cms version' to determine the installed software version
    Affected if Version matches 1.9, 2.0, 2.1, 2.2, 2.3, or 2.4
  2. Review network interface binding configuration
    Examine the CMS network configuration via the web interface under Network > Interfaces or via API call to /api/v1/networkInterfaces. Identify which interfaces are configured as 'external' versus 'internal' and verify internal interfaces are not bound to the external-facing IP address
    Affected if Internal interfaces (such as those serving configuration files, databases, or meeting data) are bound to or accessible via the external interface
  3. Verify TURN service TLS configuration
    Check the TURN server settings in the web interface under Call Bridge > TURN or via API call to /api/v1/turn. Determine if TURN service is enabled with TLS encryption
    Affected if TURN service with TLS is enabled on an externally accessible interface
  4. Test external access to sensitive endpoints
    From an external network location, attempt HTTP/HTTPS connections to common configuration and database paths such as /api/v1/config, /api/v1/databases, or port 443/8443 to determine if internal data is exposed
    Affected if Configuration files, database files, or meeting information are accessible without authentication from external networks

The environment is affected if running Cisco Meeting Server version 2.4 or earlier and internal interfaces or TURN services are exposed on externally accessible network interfaces.

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

Upgrade to Cisco Meeting Server software release 2.2.11 or later and review network configuration to ensure internal interfaces are not exposed on external interfaces. Additionally, if TURN service is enabled, audit TURN credentials and TLS configuration.

Fix this in Meeting Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-0262 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