Webex MeetingsApplication · Cisco

CVE-2020-3441

MEDIUM · 5.3 CVSS v3.1 Published 2020-11-18
Fix available
A fix is available. Upgrade to 3.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in Cisco Webex Meetings and Cisco Webex Meetings Server could allow an unauthenticated, remote attacker to view sensitive information from the meeting room lobby. This vulnerability is due to insufficient protection of sensitive participant information. An attacker could exploit this vulnerability by browsing the Webex roster. A successful exploit could allow the attacker to gather information about other Webex participants, such as email address and IP address, while waiting in the lobby.

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 confidence

An information disclosure vulnerability in Cisco Webex Meetings and Cisco Webex Meetings Server allows unauthenticated attackers viewing the Webex roster to access sensitive participant information (email addresses, IP addresses) that should be protected while users wait in the meeting lobby.

MitigationApply the Cisco-provided patch/update for CVE-2020-3441 to all affected Webex Meetings and Webex Meetings Server deployments to enforce proper protection of participant information in the lobby.

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
Affected:<= 40.6.11<= 40.11.3
Webex Meetings ServerApplication
Affected:< 3.0= 3.0= 4.0

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Cisco Webex Meetings version
    Locate the Webex Meetings version through the admin console, meeting site URL with '/version' appended, or by checking the installer package. Common access path: sign into Webex Administration site and view the site information or version page.
    Affected if Installed version is 40.6.11 or earlier, OR version 40.11.3 or earlier
  2. Check Cisco Webex Meetings Server version
    Access the Webex Meetings Server admin interface or check the version through the server's system information page. The version is typically visible in the admin dashboard or system settings.
    Affected if Installed version is 3.0, 4.0, or any version earlier than 3.0 (e.g., 2.x)
  3. Verify if meeting lobby feature is in use
    Determine if the Webex site or meetings are configured to use the meeting lobby/waiting room feature where participants wait before being admitted. Check site settings or meeting templates for lobby enablement.
    Affected if Lobby or waiting room feature is enabled and participants can wait before being admitted to meetings

You are affected if your Cisco Webex Meetings is version 40.6.11 or earlier or 40.11.3 or earlier, OR your Cisco Webex Meetings Server is version 3.0, 4.0, or earlier than 3.0, AND the meeting lobby feature is enabled or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.0 or later
Fixed in 3.0
Interim mitigation

Apply the Cisco-provided patch/update for CVE-2020-3441 to all affected Webex Meetings and Webex Meetings Server deployments to enforce proper protection of participant information in the lobby.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3441 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3441 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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