Webex Meetings ServerApplication · Cisco
CVE-2018-0112
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 Business Suite clients, Cisco WebEx Meetings, and Cisco WebEx Meetings Server could allow an authenticated, remote attacker to execute arbitrary code on a targeted system. The vulnerability is due to insufficient input validation by the Cisco WebEx clients. An attacker could exploit this vulnerability by providing meeting attendees with a malicious Flash (.swf) file via the file-sharing capabilities of the client. Exploitation of this vulnerability could allow arbitrary code execution on the system of a targeted user. This affects the clients installed by customers when accessing a WebEx meeting. The following client builds of Cisco WebEx Business Suite (WBS30, WBS31, and WBS32), Cisco WebEx Meetings, and Cisco WebEx Meetings Server are impacted: Cisco WebEx Business Suite (WBS31) client builds prior to T31.23.2, Cisco WebEx Business Suite (WBS32) client builds prior to T32.10, Cisco WebEx Meetings with client builds prior to T32.10, Cisco WebEx Meetings Server builds prior to 2.8 MR2. Cisco Bug IDs: CSCvg19384, CSCvi10746.
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 confidenceThis vulnerability in Cisco WebEx client applications stems from insufficient input validation when processing Flash (.swf) files shared through the file-sharing feature. An authenticated remote attacker can deliver a malicious .swf file to meeting attendees, which when processed by the vulnerable client executes arbitrary code on the target user's system with the privileges of the logged-in 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 ServerApplication
= 2.7= 2.8= 3.0
Webex MeetingsApplication
= t31
Webex Business Suite 31Application
< t31.23.2
Webex Business Suite 32Application
< t32.10CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/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 Cisco WebEx productCheck installed programs or application metadata to determine if Cisco WebEx Meetings Server, Cisco WebEx Meetings, or Cisco WebEx Business Suite is installedAffected if Any of these three products is installed
-
Determine installed version for WebEx Business Suite 31Locate the installed version number for Cisco WebEx Business Suite 31 (typically visible in the application or in Add/Remove Programs)Affected if Version is less than t31.23.2 (for example, t31.22, t31.20, etc.)
-
Determine installed version for WebEx Business Suite 32Locate the installed version number for Cisco WebEx Business Suite 32 (typically visible in the application or in Add/Remove Programs)Affected if Version is less than t32.10 (for example, t32.9, t32.8, etc.)
-
Determine installed version for WebEx MeetingsLocate the installed version number for Cisco WebEx Meetings (typically visible in the application or in Add/Remove Programs)Affected if Version is equal to t31 (any t31.x variant before t31.23.2 on business suite, or exactly t31 for meetings)
-
Determine installed version for WebEx Meetings ServerCheck the server version through administrative interface or system documentation for Cisco WebEx Meetings ServerAffected if Version is exactly 2.7, 2.8, or 3.0
The user is affected if they have any Cisco WebEx product installed with a version matching the affected ranges: Business Suite 31 < t31.23.2, Business Suite 32 < t32.10, Meetings = t31, or Meetings Server = 2.7/2.8/3.0.
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.
dbcve · scopedUpgrade affected Cisco WebEx clients to the patched versions: WBS31 to T31.23.2 or later, WBS32 to T32.10 or later, WebEx Meetings to T32.10 or later, and WebEx Meetings Server to 2.8 MR2 or later.
Upgrade to T31.23.2 (WBS31), T32.10 (WBS32/WebEx Meetings), or 2.8 MR2 (WebEx Meetings Server) depending on product
- Identify the current WebEx client build version being used (WBS31, WBS32, WebEx Meetings client, or WebEx Meetings Server)
- For Cisco WebEx Business Suite (WBS31) clients: Upgrade to client build T31.23.2 or later
- For Cisco WebEx Business Suite (WBS32) clients: Upgrade to client build T32.10 or later
- For Cisco WebEx Meetings clients: Upgrade to client build T32.10 or later
- For Cisco WebEx Meetings Server: Upgrade to version 2.8 MR2 or later
- Verify the upgrade was successful by checking the new client build version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Webex Meetings Server
Scoped from the published advisory
- Consultation3.0 h
- Implementation5.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0112 — 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-0112 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