# CVE-2020-3142: Cisco Webex Meetings Suite and Cisco Webex Meetings Online Unauthenticated Meeting Join Vulnerability

> Unauthenticated remote attackers can join password-protected Webex meetings via mobile app deep links, bypassing authentication controls.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-58r3-xwfg-7j3x

## What is CVE-2020-3142?

CVE-2020-3142 is a high-severity authentication bypass vulnerability in Cisco Webex Meetings Online, published on 26 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco Webex Meetings Suite sites and Cisco Webex Meetings Online sites could allow an unauthenticated, remote attendee to join a password-protected meeting without providing the meeting password. The connection attempt must initiate from a Webex mobile application for either iOS or Android. The vulnerability is due to unintended meeting information exposure in a specific meeting join flow for mobile applications. An unauthorized attendee could exploit this vulnerability by accessing a known meeting ID or meeting URL from the mobile device’s web browser. The browser will then request to launch the device’s Webex mobile application. A successful exploit could allow the unauthorized attendee to join the password-protected meeting. The unauthorized attendee will be visible in the attendee list of the meeting as a mobile attendee. Cisco has applied updates that address this vulnerability and no user action is required. This vulnerability affects Cisco Webex Meetings Suite sites and Cisco Webex Meetings Online sites releases earlier than 39.11.5 and 40.1.3.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Cisco Webex Meetings Online.

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

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

## Is CVE-2020-3142 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings Online

- [CVE-2018-0287](https://insights.sbomify.com/CVE-2018-0287/): Code injection in Cisco WebEx Advanced Recording Format Player (high 8.8)
- [CVE-2019-1637](https://insights.sbomify.com/CVE-2019-1637/): Cisco Webex Network Recording Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-1638](https://insights.sbomify.com/CVE-2019-1638/): Cisco Webex Network Recording Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-1639](https://insights.sbomify.com/CVE-2019-1639/): Cisco Webex Network Recording Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-1640](https://insights.sbomify.com/CVE-2019-1640/): Cisco Webex Network Recording Player Arbitrary Code Execution Vulnerabilities (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3142 is a high-severity authentication bypass vulnerability in Cisco Webex Meetings Online, published on 26 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3142 in the wild and no public exploit code.

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

## Sources

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

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