# CVE-2020-3419: Cisco Webex Meetings and Cisco Webex Meetings Server Ghost Join Vulnerability

> Unauthenticated attackers can join Webex meetings invisibly with full access if they possess valid join credentials, bypassing participant visibility controls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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 Nov 2020
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-gq3h-3p4j-vffv

## What is CVE-2020-3419?

CVE-2020-3419 is a medium-severity authentication bypass vulnerability in Cisco Webex Meetings Server, published on 18 Nov 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 Cisco Webex Meetings and Cisco Webex Meetings Server could allow an unauthenticated, remote attacker to join a Webex session without appearing on the participant list. This vulnerability is due to improper handling of authentication tokens by a vulnerable Webex site. An attacker could exploit this vulnerability by sending crafted requests to a vulnerable Cisco Webex Meetings or Cisco Webex Meetings Server site. A successful exploit requires the attacker to have access to join a Webex meeting, including applicable meeting join links and passwords. The attacker could then exploit this vulnerability to join meetings, without appearing in the participant list, while having full access to audio, video, chat, and screen sharing capabilities.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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

It affects 1 product.


Products: Cisco Webex Meetings Server.

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

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

## Is CVE-2020-3419 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings Server

- [CVE-2017-12367](https://insights.sbomify.com/CVE-2017-12367/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2015-0589](https://insights.sbomify.com/CVE-2015-0589/): Command injection in n/a (critical 9.0)
- [CVE-2017-3794](https://insights.sbomify.com/CVE-2017-3794/): Cross-site request forgery in Cisco WebEx Meetings Server 2.6 (high 8.8)
- [CVE-2016-1448](https://insights.sbomify.com/CVE-2016-1448/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-1446](https://insights.sbomify.com/CVE-2016-1446/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3419 and fix it if it is affected.

What it is: CVE-2020-3419 is a medium-severity authentication bypass vulnerability in Cisco Webex Meetings Server, published on 18 Nov 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-3419 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings Server. 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-3419/ (Markdown: https://insights.sbomify.com/CVE-2020-3419/index.md)
```

## Sources

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

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