Webex Meetings OnlineApplication · Cisco
CVE-2018-15412
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 Cisco Webex Network Recording Player for Microsoft Windows and the Cisco Webex Player for Microsoft Windows could allow an attacker to execute arbitrary code on an affected system. The vulnerability exist because the affected software improperly validates Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker could exploit this vulnerability by sending a user a malicious ARF or WRF file via a link or an email attachment and persuading the user to open the file by using the affected software. A successful exploit could allow the attacker to execute arbitrary code on the affected 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 · moderate confidenceThe Cisco Webex Network Recording Player and Webex Player for Windows improperly validate Advanced Recording Format (ARF) and Webex Recording Format (WRF) files, allowing specially crafted malicious files to trigger arbitrary code execution when opened by users.
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
Webex Meetings ServerApplication
= 2.5= 2.5.1.29= 2.6= 2.7= 2.7.1= 2.8
Webex Business Suite 32Application
< 32.15.20
Webex Business Suite 33Application
< 33.3CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Webex Player installationSearch for 'Webex Player' or 'Webex Network Recording Player' in Program Files directories, or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Webex' and 'Player'Affected if No Webex Player installation found means not affected by this CVE
-
Identify installed Webex Player versionRight-click the player executable (typically named something like 'WebexPlayer.exe' or 'gpcplayer.exe') in the installation folder, select Properties, and view the File Version tab. Alternatively, check the Windows Registry under the uninstall key for the DisplayVersion value.Affected if Version cannot be determined or does not match the installed product means check manually against affected versions
-
Compare version against affected rangesFor Cisco Webex Meetings Online: verify version < 1.3.37. For Cisco Webex Meetings Server: verify version equals 2.5, 2.5.1.29, 2.6, 2.7, 2.7.1, or 2.8. For Cisco Webex Business Suite 32: verify version < 32.15.20. For Cisco Webex Business Suite 33: verify version < 33.3Affected if Installed version falls within any of these ranges indicates the system is vulnerable
-
Confirm ARF/WRF file handling is enabledThe player processes ARF and WRF recording files by default when users open them. No specific configuration toggle needs to be checked - the vulnerability applies if the player can be used to open these file types.Affected if Player is installed and can open ARF/WRF files means the exploit vector exists
A system is affected if Cisco Webex Player for Windows is installed and its version falls within the specified vulnerable ranges, allowing specially crafted ARF/WRF files to execute arbitrary code when opened by users.
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.3
Organizations should deploy available Cisco patches for the Webex players, implement email/URL filtering to block malicious ARF/WRF attachments, and train users to avoid opening untrusted recording files.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15412 — 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-15412 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