dbcve.org
Webex TeamsApplication · Cisco

CVE-2019-1636

HIGH · 7.8 CVSS v3.0 Published 2019-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 the Cisco Webex Teams client, formerly Cisco Spark, could allow an attacker to execute arbitrary commands on a targeted system. This vulnerability is due to unsafe search paths used by the application URI that is defined in Windows operating systems. An attacker could exploit this vulnerability by convincing a targeted user to follow a malicious link. Successful exploitation could cause the application to load libraries from the directory targeted by the URI link. The attacker could use this behavior to execute arbitrary commands on the system with the privileges of the targeted user if the attacker can place a crafted library in a directory that is accessible to the vulnerable system.

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 DLL hijacking vulnerability in Cisco Webex Teams for Windows allows arbitrary code execution through unsafe library loading paths. When the application processes a specially crafted URI link, it loads DLLs from the directory specified in the URI instead of secure system paths, enabling an attacker to execute malicious code with the user's privileges.

MitigationApply the vendor patch when available. Until then, instruct users to avoid clicking untrusted links and consider restricting write access to directories in the Webex Teams executable's search path to prevent attacker-placed libraries.

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:= 3.0.4533

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

CVSS:3.0/AV:L/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. Check if Cisco Webex Teams is installed
    Open Programs and Features (appwiz.cpl) or check the standard installation directory for an entry named Cisco Webex Teams or Webex Teams
    Affected if The application is not listed or not found on the system, then this CVE does not apply
  2. Identify the installed version of Cisco Webex Teams
    Right-click the Cisco Webex Teams executable, select Properties, and view the File Version field on the Details tab. Alternatively, run 'wmic product get name,version' or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the Webex Teams entry
    Affected if The installed version cannot be determined or is not visible in standard locations
  3. Compare your installed version to the affected version
    Match the version you found against the affected version 3.0.4533 exactly
    Affected if The installed version is exactly 3.0.4533, indicating the environment matches the vulnerable version
  4. Verify URI handling capability is present
    Check if the Webex Teams URI handler is registered on the system by examining the Windows Registry under HKCR\webex or by attempting to invoke a webex:// URI and confirming the application responds
    Affected if The URI handler is registered and the application processes URI schemes, enabling the attack vector described in the CVE

A system is affected only if Cisco Webex Teams version 3.0.4533 is installed AND the URI handling functionality is present and operational on the Windows system.

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 when available. Until then, instruct users to avoid clicking untrusted links and consider restricting write access to directories in the Webex Teams executable's search path to prevent attacker-placed libraries.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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