CVE-2020-3142
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Cisco Webex mobile applications allows unauthenticated attendees to join password-protected meetings without providing the password. The issue stems from unintended meeting information exposure in the mobile app join flow— when a user clicks a meeting URL from a mobile browser, the Webex mobile app launches without requiring password authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 39.11.5< 40.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Webex Meetings Online usageIdentify whether your organization uses Cisco Webex Meetings Online for video conferencing. Check your Webex account details or contact your Webex administrator.Affected if Your organization does not use Cisco Webex Meetings Online, as this CVE specifically affects that service.
-
Identify the Webex Meetings Suite versionAccess the Webex site administration panel or contact your Webex administrator to retrieve the current version of your Webex Meetings Suite deployment.Affected if Unable to determine the version, as version information is required to assess vulnerability status.
-
Compare installed version against CVE-2020-3142 affected rangesCompare the identified version against the vulnerable ranges: versions earlier than 39.11.5, or versions earlier than 40.1.3. Note that versions 39.11.5 and above, or 40.1.3 and above, contain the fix.Affected if Your Webex Meetings Suite version is earlier than 39.11.5 OR earlier than 40.1.3.
-
Verify password requirement in mobile app join flowFrom a mobile browser, click a password-protected meeting URL and observe whether the Webex mobile app launches and grants access without prompting for a password. This test should be conducted in a test meeting with administrator awareness.Affected if The mobile app grants meeting access without presenting a password prompt after clicking a meeting URL from a mobile browser, indicating the vulnerability may still be present.
Your environment is affected if you use Cisco Webex Meetings Online with a version earlier than 39.11.5 or earlier than 40.1.3, where clicking a meeting URL from a mobile browser bypasses password authentication in the mobile app.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data39.11.540.1.3
No client-side action required. Cisco has already applied server-side updates addressing this vulnerability. Organizations should verify their Webex Meetings Suite is on version 39.11.5 or later, or version 40.1.3 or later.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3142 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data