Webex Meetings OnlineApplication · Cisco
CVE-2018-15418
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 · high confidenceThe vulnerability exists in Cisco Webex Network Recording Player and Webex Player for Windows due to improper validation of Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker can send a malicious ARF or WRF file (via link or email attachment) and convince a user to open it in the affected player, leading to arbitrary code execution with the user's privileges.
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.10
Webex Business Suite 33Application
< 33.5
Webex Business Suite 31Application
< 31.23.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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.
-
Check if Cisco Webex Player is installedOpen Programs and Features (appwiz.cpl) or check the installation directory for 'Cisco Webex Network Recording Player' or 'Webex Player' entriesAffected if The player software appears in installed programs or directories
-
Identify the installed version numberRight-click the Webex player executable (typically named something like 'WebexPlayer.exe' or 'atgstubsvr.exe' in the Webex program folder), select Properties, then check the Details tab for the File Version, or run 'Get-ItemProperty' in PowerShell on the executableAffected if A version number is returned that can be compared to the affected ranges
-
Compare version against affected rangesFor Webex Meetings Online: check if version < 1.3.37. For Webex Meetings Server: check if version equals 2.5, 2.5.1.29, 2.6, 2.7, 2.7.1, or 2.8. For Business Suite 32: check if version < 32.15.10. For Business Suite 33: check if version < 33.5. For Business Suite 31: check if version < 31.23.0Affected if The installed version falls within any of the listed affected versions or ranges
-
Confirm ARF/WRF file handling capability existsSearch the system for .arf or .wrf file associations (check HKEY_CLASSES_ROOT\.arf and HKEY_CLASSES_ROOT\.wrf in the registry, or look for these file types in File Explorer)Affected if The system has file associations registered for .arf or .wrf files pointing to the Webex player
A user is affected if the Cisco Webex Player is installed with a version that falls within any of the specified affected ranges AND the player can open ARF or WRF files.
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.3731.23.032.15.10
Users should refrain from opening untrusted ARF or WRF files. Organizations should identify and update affected Cisco Webex players to patched versions and consider endpoint detection solutions to identify malicious file attempts.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation3.0 h
- Implementation5.0 h
- Testing3.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15418 — 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-15418 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