Webex MeetingsApplication · Cisco
CVE-2021-1372
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 and Webex Productivity Tools for Windows could allow an authenticated, local attacker to gain access to sensitive information on an affected system. This vulnerability is due to the unsafe usage of shared memory 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. Note: To exploit this vulnerability, an attacker must have valid credentials on a Microsoft Windows end-user system and must log in after another user has already authenticated with Webex on the same end-user system.
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 Meetings Desktop App and Webex Productivity Tools for Windows allows an authenticated local attacker to read sensitive information from unsafe shared memory usage. An attacker with valid Windows credentials who logs in after another user has authenticated with Webex can exploit this by running a local application designed to read shared memory, potentially retrieving usernames, meeting information, or authentication tokens.
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.6< 40.10
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
- 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.
-
Identify installed Webex product and versionOpen Windows Control Panel > Programs and Features, or right-click the Webex icon in the system tray and select 'About Webex Meetings' to view the installed version numberAffected if The installed version is Cisco Webex Meetings Desktop App < 40.6, < 40.10, or Webex Productivity Tools for Windows, or Cisco Webex Meetings Server version < 4.0 or = 4.0
-
Check Windows user account configurationOpen Computer Management > Local Users and Groups > Users, or run 'net user' in Command Prompt to list all local user accounts on the systemAffected if Multiple local user accounts exist on the Windows machine where Webex is installed
-
Verify shared memory exposure riskUse Sysinternals Process Explorer or RAM map tools to inspect Webex processes (such as webexm.exe or atimf.exe) and their shared memory sections. Look for objects with 'SECURITY' or 'AUTH' in the name that may contain credentials or tokensAffected if Shared memory sections in Webex processes contain readable sensitive data without proper access controls
-
Confirm multi-user session usageCheck Windows Event Viewer for login events showing multiple users accessing the same machine, or review terminal services logs for concurrent or sequential user sessionsAffected if More than one user account has logged into the Windows system where Webex was previously authenticated
You are affected if Cisco Webex Meetings Desktop App, Webex Productivity Tools, or Cisco Webex Meetings Server is installed at a version below 40.6 (or below 40.10 for specific branches) or version 4.0 on a Windows system with multiple user accounts that have logged in sequentially.
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 data4.040.640.10
Apply vendor-provided patches from Cisco for affected Webex products. Ensure proper user session isolation and avoid shared local user accounts. Consider implementing additional controls to restrict local memory access or monitor for processes attempting shared memory reads.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1372 — 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-2021-1372 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