Webex Meetings OnlineApplication · Cisco
CVE-2018-0422
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 the folder permissions of Cisco Webex Meetings client for Windows could allow an authenticated, local attacker to modify locally stored files and execute code on a targeted device with the privilege level of the user. The vulnerability is due to folder permissions that grant a user the permission to read, write, and execute files in the Webex folders. An attacker could exploit this vulnerability to write malicious files to the Webex client directory, affecting all other users of the targeted device. A successful exploit could allow a user to execute commands with elevated privileges. Attacks on single-user systems are less likely to occur, as the attack must be carried out by the user on the user's own system. Multiuser systems have a higher risk of exploitation because folder permissions have an impact on all users of the device. For an attacker to exploit this vulnerability successfully, a second user must execute the locally installed malicious file to allow remote code execution to occur.
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 client for Windows has insecure folder permissions that grant users read, write, and execute access to Webex directories. An authenticated local attacker can place malicious files in these folders, which will be executed by other users on multiuser systems, achieving code execution at the privilege level of the victim user.
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 Meetings OnlineApplication
< 1.3.37= t31.20= t31.20.2
Webex Meetings ServerApplication
<= 3.0= 3.0
Webex Business Suite 32Application
< 32.15.20
Webex Business Suite 33Application
< 33.4
Webex Business Suite 31Application
all versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Webex client versionOpen the Windows Control Panel, go to Programs and Features, locate Cisco Webex Meetings in the list, and note the installed version numberAffected if The version number is lower than 1.3.37, equals t31.20 or t31.20.2 (for Webex Meetings Online); is 3.0 or lower (for Webex Meetings Server); is below 32.15.20 (for Business Suite 32); is below 33.4 (for Business Suite 33); or is any version (for Business Suite 31)
-
Locate Webex installation directoriesSearch for directories named Webex or containing Cisco Webex software on the system drive, typically found under Program FilesAffected if Webex directories exist on the system and are accessible to standard users
-
Examine folder permissions on Webex directoriesRight-click each Webex installation folder, select Properties, go to the Security tab, and review the permissions for standard user accounts or the Users groupAffected if Standard users or the Users group are granted Write or Execute permissions to Webex directories
-
Confirm multi-user system usageCheck if more than one user account exists on the Windows system by opening Computer Management and reviewing Local Users and Groups, or check user profiles in System PropertiesAffected if Multiple user accounts are present on the system and share access to the Webex installation directories
A system is affected if the installed Cisco Webex client version falls within the affected ranges AND standard users have Write or Execute permissions on Webex directories in a multi-user Windows environment
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 data1.3.3732.15.2033.4
Restrict folder permissions on Webex client directories to remove unnecessary write/execute access for standard users; apply any available Cisco patch for Webex Meetings client.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0422 — 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-2018-0422 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