Webex TeamsApplication · Cisco

CVE-2018-0387

HIGH · 8.8 CVSS v3.1 Published 2018-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Teams (for Windows and macOS) could allow an unauthenticated, remote attacker to execute arbitrary code on the user's device, possibly with elevated privileges. The vulnerability occurs because Cisco Webex Teams does not properly sanitize input. An attacker could exploit the vulnerability by sending a user a malicious link and persuading the user to follow the link. A successful exploit could allow the attacker to execute arbitrary code on the user's system. Cisco Bug IDs: CSCvh66250.

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 remote code execution vulnerability in Cisco Webex Teams for Windows and macOS stems from improper input sanitization, allowing unauthenticated attackers to send malicious links that, when clicked by users, can execute arbitrary code on the affected system, potentially with elevated privileges.

MitigationApply the vendor patch from Cisco (Bug CSCvh66250) by updating Cisco Webex Teams to the latest version; users should avoid clicking untrusted links until the patch is applied.

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 TeamsApplication
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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Cisco Webex Teams is installed
    On Windows: Check for 'Cisco Webex Teams' in Add/Remove Programs or look for the application in Program Files. On macOS: Check /Applications folder for 'Webex Teams.app' or use Spotlight to search for the application.
    Affected if The application is present on the system
  2. Identify the installed version
    On Windows: Right-click the Webex Teams icon in the system tray, select 'Check for Updates' or look in the application's 'Help' > 'About' section. On macOS: Right-click 'Webex Teams.app' in Applications, select 'Get Info' or check within the app's preferences under 'Help' > 'About'.
    Affected if Any version number is displayed, confirming the software is running
  3. Verify the application processes messages or links
    Check if the user can receive and click on links within Webex Teams messages. The vulnerability is triggered when a user clicks a malicious link in a message.
    Affected if The application is configured to allow clicking links in messages
  4. Check for recent application activity
    Review recent Webex Teams connection logs or the application's activity window to confirm the software has been used recently, indicating active exposure to the vulnerability.
    Affected if The application shows recent message or meeting activity

If Cisco Webex Teams is installed and operational on Windows or macOS, the environment is affected by this vulnerability since all versions are impacted.

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 vendor patch from Cisco (Bug CSCvh66250) by updating Cisco Webex Teams to the latest version; users should avoid clicking untrusted links until the patch is applied.

Fix this in Webex Teams Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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