dbcve.org
Webex Meetings ServerApplication · Cisco

CVE-2018-0110

HIGH · 8.1 CVSS v3.0 Published 2018-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 WebEx Meetings Server could allow an authenticated, remote attacker to access the remote support account even after it has been disabled via the web application. The vulnerability is due to a design flaw in Cisco WebEx Meetings Server, which would not disable access to specifically configured user accounts, even after access had been disabled in the web application. An attacker could exploit this vulnerability by connecting to the remote support account, even after it had been disabled at the web application level. An exploit could allow the attacker to modify server configuration and gain access to customer data. Cisco Bug IDs: CSCvg46741.

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 design flaw in Cisco WebEx Meetings Server allows authenticated remote attackers to access remote support accounts even after those accounts have been disabled through the web application interface. The web application-level disabling does not actually revoke authentication access at the system level, allowing continued access to modify server configurations and exfiltrate customer data.

MitigationApply Cisco's vendor patch for CSCvg46741 to ensure web application-level account disabling properly revokes authentication access. Until patched, implement additional access controls and monitoring on remote support accounts.

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

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

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 WebEx Meetings Server installation
    Identify the product running in your environment by checking the server banner, installed packages, or administrative interface. Look for 'Cisco WebEx Meetings Server' or 'CWMS' in system information.
    Affected if The system is confirmed to be Cisco WebEx Meetings Server of any version.
  2. Locate remote support accounts
    Access the administrative web interface and navigate to the user or account management section. Look for accounts with roles such as 'Remote Support', 'Support', or administrative accounts used for vendor support purposes.
    Affected if Remote support accounts exist in the system, regardless of their enabled/disabled status.
  3. Verify disabled account status via web interface
    In the web-based administrative console, check which remote support accounts show as 'disabled', 'inactive', or have been toggled off through the account management UI.
    Affected if Any remote support accounts have been disabled through the web application interface.
  4. Test authentication access for disabled accounts
    Attempt to authenticate using the supposedly disabled remote support account credentials against the system's authentication endpoints (e.g., login page, API, or SSO). Compare authentication behavior against a known-good disabled account.
    Affected if The disabled remote support account can still successfully authenticate and gain access to the system.
  5. Review account access logs for disabled accounts
    Examine authentication logs, audit logs, or access logs for the Cisco WebEx Meetings Server. Look for successful logins, configuration changes, or data access events originating from accounts listed as disabled in the web interface.
    Affected if Any log entries show successful authentication or system access by accounts that are disabled in the web interface.

If remote support accounts disabled via the web interface can still authenticate or have logged activity after being disabled, the environment is affected by this vulnerability.

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 Cisco's vendor patch for CSCvg46741 to ensure web application-level account disabling properly revokes authentication access. Until patched, implement additional access controls and monitoring on remote support accounts.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0110 — 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-0110 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