# CVE-2019-1674: Cisco Webex Meetings Desktop App and Cisco Webex Productivity Tools Update Service Command Injection Vulnerability

> Local attackers can execute arbitrary commands with SYSTEM privileges via the update service, potentially escalating privileges in Active Directory environments.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-r6w6-ww22-j2ff

## What is CVE-2019-1674?

CVE-2019-1674 is a high-severity command injection vulnerability in Cisco Webex Meetings, published on 28 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the update service of Cisco Webex Meetings Desktop App and Cisco Webex Productivity Tools for Windows could allow an authenticated, local attacker to execute arbitrary commands as a privileged user. The vulnerability is due to insufficient validation of user-supplied parameters. An attacker could exploit this vulnerability by invoking the update service command with a crafted argument. An exploit could allow the attacker to run arbitrary commands with SYSTEM user privileges. While the CVSS Attack Vector metric denotes the requirement for an attacker to have local access, administrators should be aware that in Active Directory deployments, the vulnerability could be exploited remotely by leveraging the operating system remote management tools. This vulnerability is fixed in Cisco Webex Meetings Desktop App Release 33.6.6 and 33.9.1 releases. This vulnerability is fixed in Cisco Webex Productivity Tools Release 33.0.7.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 3 products.


Products: Cisco Webex Meetings, Cisco Webex Meetings Online, Cisco Webex Productivity Tools.

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

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

## Is CVE-2019-1674 being exploited?

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

Public exploit code:

- Cisco WebEx Meetings < 33.6.6 / < 33.9.1 - Privilege Escalation (exploitdb)

## 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-1674 and fix it if it is affected.

What it is: CVE-2019-1674 is a high-severity command injection vulnerability in Cisco Webex Meetings, published on 28 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1674 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-1674/ (Markdown: https://insights.sbomify.com/CVE-2019-1674/index.md)
```

## Sources

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

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