Webex Meetings OnlineApplication · Cisco
CVE-2018-15411
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 Cisco Webex Network Recording Player and Webex Player for Windows improperly validate Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker can embed malicious code in these recording files that executes arbitrary code when a user opens the file in the affected player software.
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.30
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.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.
-
Identify if Webex recording player is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion' via PowerShell. Look for 'Cisco Webex Network Recording Player' or 'Webex Player' in the installed programs list.Affected if The software appears in the installed programs list with a version that matches the affected ranges.
-
Determine the exact version of Webex Network Recording PlayerRight-click the installed player executable (typically in C:\Program Files\Webex\Webex Recording Player or similar path), select Properties, and check the File Version on the Details tab. Alternatively, right-click the player in Programs and Features and select 'Change' or 'Properties' to view the version.Affected if Version is Cisco Webex Meetings Online < 1.3.37, or Cisco Webex Meetings Server versions 2.5, 2.5.1.29, 2.6, 2.7, 2.7.1, or 2.8, or Cisco Webex Business Suite 32 <= 32.15.30, or Cisco Webex Business Suite 33 < 33.4.
-
Check for Webex Business Suite versionIf Webex Business Suite is deployed, open the Webex Administration site or check the installer package used. The version is typically displayed in the Webex client under Help > About Webex, or in the Windows installed programs list as 'Cisco Webex Business Suite' with a version number.Affected if Version shows 32.x and is <= 32.15.30, or shows 33.x and is < 33.4.
-
Verify .arf and .wrf file type associationsOpen Command Prompt and run 'assoc .arf' and 'assoc .wrf' to see which application is associated with these file extensions. Also check in Windows Explorer by clicking a .arf or .wrf file and observing which player opens it.Affected if The files are set to open with Cisco Webex Network Recording Player or Webex Player, indicating the vulnerable component is in use.
You are affected if Cisco Webex Network Recording Player, Webex Player for Windows, or Webex Business Suite is installed with a version matching any of the affected ranges listed.
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.3733.4
Deploy the Cisco patch when available. Until then, instruct users not to open untrusted ARF/WRF files received via email or links, and consider blocking these file types at the email gateway.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15411 — 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-15411 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