Webex MeetingsApplication · Cisco
CVE-2020-3361
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 and Cisco Webex Meetings Server could allow an unauthenticated, remote attacker to gain unauthorized access to a vulnerable Webex site. The 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. If successful, the attacker could gain the privileges of another user within the affected Webex site.
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 · moderate confidenceThis is an authentication bypass vulnerability in Cisco Webex Meetings and Cisco Webex Meetings Server caused by improper handling of authentication tokens. An unauthenticated, remote attacker can send crafted requests to gain unauthorized access to a vulnerable Webex site and obtain the privileges of another user on the affected system.
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
Webex MeetingsApplication
<= 39.5.25>= 40.1.0, <= 40.4.10= 40.6.0
Webex Meetings ServerApplication
< 4.0= 4.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if Cisco Webex Meetings is running in the environmentDetermine whether Cisco Webex Meetings or Cisco Webex Meetings Server is deployed. This may be a cloud-hosted service, an on-premises installation, or a hybrid deployment. Check with your IT asset inventory or documentation if Webex Meetings is used.Affected if The organization uses Cisco Webex Meetings or Cisco Webex Meetings Server as their web conferencing platform.
-
Determine the installed version of Cisco Webex MeetingsLocate the version information for your Cisco Webex Meetings deployment. For cloud-hosted Webex, check the admin portal or contact Cisco support. For Cisco Webex Meetings Server (on-premises), check the management interface, release notes, or system documentation for the currently installed version number.Affected if The exact version cannot be determined from available documentation or admin interfaces.
-
Determine the installed version of Cisco Webex Meetings ServerIf using Cisco Webex Meetings Server on-premises, check the version through the administrative console, system information page, or the installed software package. Note the major and minor version numbers (for example, 3.0, 4.0, etc.).Affected if The exact version cannot be determined from available documentation or admin interfaces.
-
Compare your version against affected ranges for Cisco Webex MeetingsFor Cisco Webex Meetings: Check if your version falls into any of these ranges: version 39.5.25 or lower, OR between 40.1.0 and 40.4.10 inclusive, OR exactly version 40.6.0. If your version is higher than 40.6.0, you are likely not affected.Affected if Your Cisco Webex Meetings version is 39.5.25 or lower, between 40.1.0 and 40.4.10, or exactly 40.6.0.
-
Compare your version against affected ranges for Cisco Webex Meetings ServerFor Cisco Webex Meetings Server: Check if your version is less than 4.0 or exactly 4.0. If your version is 4.0 or higher, you are likely not affected.Affected if Your Cisco Webex Meetings Server version is any release before 4.0, or exactly version 4.0.
If Cisco Webex Meetings or Cisco Webex Meetings Server is running and the installed version falls within the affected ranges listed above, the environment is vulnerable to CVE-2020-3361.
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.
dbcve · scoped4.0
Apply the relevant Cisco security patch for CVE-2020-3361 and review authentication logs for signs of exploitation. Consider rotating session tokens and credentials as a precautionary measure.
Webex Meetings: 39.6.0+, 40.5.0+, 40.7.0+ | Webex Meetings Server: 4.0 MR1+ or 4.1+
- 1. Identify the currently installed Webex Meetings or Webex Meetings Server version
- 2. For Webex Meetings (39.x line): Upgrade to version 39.6.0 or later
- 3. For Webex Meetings (40.1.0 - 40.4.10): Upgrade to version 40.5.0 or later
- 4. For Webex Meetings (40.6.0): Upgrade to version 40.7.0 or later
- 5. For Webex Meetings Server (< 4.0 or = 4.0): Upgrade to version 4.0 MR1 or later, or migrate to version 4.1+
- 6. After upgrade, verify that authentication tokens are being properly validated
- 7. Review Webex access logs for any suspicious activity around the time of the vulnerability disclosure
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3361 — 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-3361 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