# CVE-2020-3342: Cisco Webex Meetings Desktop App for Mac Update Feature Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into visiting malicious sites that bypass cryptographic validation during software updates.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jun 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-4f94-mvx7-c9mf

## What is CVE-2020-3342?

CVE-2020-3342 is a high-severity code injection vulnerability in Cisco Webex Meetings, published on 18 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the software update feature of Cisco Webex Meetings Desktop App for Mac could allow an unauthenticated, remote attacker to execute arbitrary code on an affected system. The vulnerability is due to improper validation of cryptographic protections on files that are downloaded by the application as part of a software update. An attacker could exploit this vulnerability by persuading a user to go to a website that returns files to the client that are similar to files that are returned from a valid Webex website. The client may fail to properly validate the cryptographic protections of the provided files before executing them as part of an update. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of the user.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2020-3342?

It affects 1 product.


Products: Cisco Webex Meetings.

## How do I fix CVE-2020-3342?

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

## Is CVE-2020-3342 being exploited?

There is no known exploitation of CVE-2020-3342 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-2020-3342 and fix it if it is affected.

What it is: CVE-2020-3342 is a high-severity code injection vulnerability in Cisco Webex Meetings, published on 18 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-3342 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-2020-3342/ (Markdown: https://insights.sbomify.com/CVE-2020-3342/index.md)
```

## Sources

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

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