Cisco Webex Teams URI Handler Insecure Library Loading Vulnerability

published 2019-01-23 7y ago modified 2026-06-17 4mo ago also EUVD-2019-10193

cvss: 7.8; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 46.9%; EPSS 46.9% chance of exploitation in 30 days, percentile 98%
public exploits: 0; none known

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.

Is CVE-2019-1636 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2024-11-20)

Exploit prediction

46.89% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

Cisco Cisco Webex Teams

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

tools.cisco.com /security/center/content/CiscoSecurityAdvisory/cisco-sa-20190123-webex-teams
vendor-advisory
securityfocus.com /bid/106718
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-1636
NVD CVE-2019-1636

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.