# CVE-2019-16001: Cisco Webex Teams for Windows DLL Hijacking Vulnerability

> An authenticated local attacker can execute arbitrary code with another user's privileges via DLL hijacking in Cisco Webex Teams for Windows.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Nov 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-fvwq-fqr3-fwqf

## What is CVE-2019-16001?

CVE-2019-16001 is a medium-severity code injection vulnerability in Cisco Webex Meetings, published on 26 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the loading mechanism of specific dynamic link libraries in Cisco Webex Teams for Windows could allow an authenticated, local attacker to perform a DLL hijacking attack. To exploit this vulnerability, the attacker would need to have valid credentials on the Windows system. The vulnerability is due to insufficient validation of the resources loaded by the application at run time. An attacker could exploit this vulnerability by crafting a malicious DLL file and placing it in a specific location on the targeted system. The malicious DLL file would execute when the vulnerable application is launched. A successful exploit could allow the attacker to execute arbitrary code on the target machine with the privileges of another user account.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2019-16001?

It affects 2 products.


Products: Cisco Webex Meetings, Cisco Webex Teams.

## How do I fix CVE-2019-16001?

No fix has been published for CVE-2019-16001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-16001 being exploited?

There is no known exploitation of CVE-2019-16001 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2017-12368](https://insights.sbomify.com/CVE-2017-12368/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12369](https://insights.sbomify.com/CVE-2017-12369/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12370](https://insights.sbomify.com/CVE-2017-12370/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12371](https://insights.sbomify.com/CVE-2017-12371/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12372](https://insights.sbomify.com/CVE-2017-12372/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16001 and fix it if it is affected.

What it is: CVE-2019-16001 is a medium-severity code injection vulnerability in Cisco Webex Meetings, published on 26 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16001 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-16001/ (Markdown: https://insights.sbomify.com/CVE-2019-16001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16001
- OSV: https://osv.dev/vulnerability/CVE-2019-16001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-16001/
Summaries are generated and may contain mistakes; the official description above is the record.