Webex Meetings OnlineApplication · Cisco
CVE-2018-15415
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 confidenceA vulnerability exists in Cisco Webex Network Recording Player and Cisco Webex Player for Microsoft Windows due to improper validation of ARF and WRF recording files. An attacker can craft a malicious recording file that, when opened by a user, allows arbitrary code execution on the affected system.
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.4CVSS 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 Cisco Webex player installationSearch for the executable files: 'WebexPlayer.exe', 'WebexNetworkRecordingPlayer.exe', or 'gpcna.exe' in typical installation directories such as C:\Program Files\Cisco Systems\ or C:\Program Files (x86)\Cisco Systems\. You can also check Start Menu shortcuts or search the system using 'where /r C:\ WebexPlayer.exe'Affected if The Webex player executables are found on the system, indicating the software is installed.
-
Retrieve the installed Webex player versionRight-click the found executable, select Properties, then go to the Details tab to view the Product Version. Alternatively, right-click the file in Windows Explorer, select Properties, and check the Version information.Affected if The version displayed is lower than the patched versions.
-
Compare against affected version rangesMatch the retrieved version number against these vulnerable ranges: Cisco Webex Meetings Online versions before 1.3.37; Cisco Webex Meetings Server versions 2.5, 2.5.1.29, 2.6, 2.7, 2.7.1, or 2.8; Cisco Webex Business Suite 32 versions before 32.15.10; Cisco Webex Business Suite 33 versions before 33.4.Affected if The installed version falls within any of these affected version ranges.
-
Check for ARF/WRF file associationOpen Windows Registry Editor and navigate to HKEY_CLASSES_ROOT\.arf or HKEY_CLASSES_ROOT\.wrf to see if these file extensions are associated with the Webex player. You can also right-click an ARF or WRF file and check the 'Opens with' program.Affected if The ARF or WRF file extensions are associated with the installed Cisco Webex player, creating a vector for exploitation.
If the Cisco Webex player is installed and its version falls within the listed affected ranges, the environment is vulnerable to arbitrary code execution when a user opens a malicious ARF or WRF file.
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.1033.4
Apply the vendor patch from Cisco to update the Webex players to a patched version. Until patched, users should not open untrusted ARF or WRF files received via links or email attachments.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation4.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15415 — 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-15415 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