Webex MeetingsApplication · Cisco
CVE-2020-3347
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 Desktop App for Windows could allow an authenticated, local attacker to gain access to sensitive information on an affected system. The vulnerability is due to unsafe usage of shared memory that is used by the affected software. An attacker with permissions to view system memory could exploit this vulnerability by running an application on the local system that is designed to read shared memory. A successful exploit could allow the attacker to retrieve sensitive information from the shared memory, including usernames, meeting information, or authentication tokens that could aid the attacker in future attacks.
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 confidenceCisco Webex Meetings Desktop App for Windows uses unsafe shared memory that can be read by local authenticated attackers. Sensitive data including usernames, meeting information, and authentication tokens are stored in unprotected shared memory regions, allowing a local attacker with memory reading capabilities to retrieve this information.
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
< 40.4.12= 40.6.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Cisco Webex Meetings is installedOpen Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed applications and search for Cisco Webex MeetingsAffected if Cisco Webex Meetings does not appear in the installed programs list
-
Determine the installed version numberLocate the Webex Meetings application in the list and note the DisplayVersion column, or right-click the application in Programs and Features and select Properties to view the Version fieldAffected if The version number cannot be determined or the application is not found
-
Compare version against affected rangesCheck if the installed version is less than 40.4.12 OR equals exactly 40.6.0. For example, versions like 40.4.10, 40.5.0, or 40.6.0 are affected. Versions 40.4.12 and later are not affected.Affected if The installed version is less than 40.4.12 or is exactly 40.6.0
-
Identify running Webex processesOpen Task Manager or run 'Get-Process | Where-Object {$_.ProcessName -like "*webex*"}' in PowerShell to see if Webex processes are active. Vulnerable shared memory is created when the application runs.Affected if Webex processes (such as webexmte.exe, atmgr.exe, or similar) are running on an affected version
A user is affected if Cisco Webex Meetings Desktop App for Windows is installed with a version less than 40.4.12 or equal to 40.6.0, and the application is actively running (creating the vulnerable shared memory regions).
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 data40.4.12
Apply the vendor patch from Cisco when available. Until then, restrict local access to systems and monitor for suspicious applications designed to read shared memory.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3347 — 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-3347 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