Webex MeetingsApplication · Cisco

CVE-2020-3342

HIGH · 8.8 CVSS v3.1 Published 2020-06-18
Fix available
A fix is available. Upgrade to 39.5.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 the software update feature of Cisco Webex Meetings Desktop App for Mac could allow an unauthenticated, remote attacker to execute arbitrary code on an affected system. The vulnerability is due to improper validation of cryptographic protections on files that are downloaded by the application as part of a software update. An attacker could exploit this vulnerability by persuading a user to go to a website that returns files to the client that are similar to files that are returned from a valid Webex website. The client may fail to properly validate the cryptographic protections of the provided files before executing them as part of an update. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of the user.

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

The Cisco Webex Meetings Desktop App for Mac has a vulnerability in its software update mechanism where cryptographic protections (likely code signing/signature validation) on downloaded update files are not properly validated. An attacker can serve malicious files from a website that mimic legitimate Webex update files, causing the vulnerable client to execute arbitrary code with the user's privileges.

MitigationApply the vendor patch from Cisco for CVE-2020-3342. Users should ensure software updates are performed only when connected to trusted networks and should verify updates originate from official Cisco Webex sources.

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:< 39.5.11

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify if Cisco Webex Meetings is installed
    Open Finder, navigate to /Applications folder and look for 'Webex Meetings.app', or run: ls /Applications | grep -i webex
    Affected if The application is present on the system
  2. Determine the installed version of Webex Meetings
    Right-click Webex Meetings.app and select 'Get Info', or run: defaults read /Applications/Webex\ Meetings.app/Contents/Info CFBundleShortVersionString
    Affected if The version displayed is below 39.5.11
  3. Compare against affected version
    Review the version number obtained; the affected range is any version lower than 39.5.11
    Affected if Installed version is 39.5.10 or earlier, or shows a version number less than 39.5.11
  4. Verify if software update mechanism is configured
    Open Webex Meetings app, go to Preferences or Settings and check if automatic updates are enabled, or inspect the app's update configuration
    Affected if Automatic updates are enabled and the client can fetch updates from network locations

A user is affected if Cisco Webex Meetings for Mac is installed with a version lower than 39.5.11 and the software update feature is active.

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 39.5.11 or later
Fixed in 39.5.11
Interim mitigation

Apply the vendor patch from Cisco for CVE-2020-3342. Users should ensure software updates are performed only when connected to trusted networks and should verify updates originate from official Cisco Webex sources.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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