Webex Meetings OnlineApplication · Cisco
CVE-2018-15416
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 contain a vulnerability due to improper validation of Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker can embed malicious code in these recording files and trick a user into opening them, achieving arbitrary code execution on the victim's 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.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.
-
Identify installed Webex playerCheck Program Files (x86) for 'Cisco Webex' folders or search for 'Network Recording Player' in the system. On Windows, also check Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Webex entries.Affected if No Webex player is found, then this CVE does not apply to the system.
-
Determine the exact versionOpen the Webex player executable (typically named 'Webex Network Recording Player.exe' or similar) and access Help > About, or check the file properties of the executable. Alternatively, query the Windows Registry for the 'DisplayVersion' value in the Webex uninstall key.Affected if Unable to determine version - manually verify the product name matches an affected Cisco Webex product.
-
Compare version against affected rangesFor Webex Meetings Online: version must be >= 1.3.37 to be patched. For Webex Meetings Server: versions 2.5, 2.5.1.29, 2.6, 2.7, 2.7.1, 2.8 are affected. For Webex Business Suite 32: version must be >= 32.15.10 to be patched. For Webex Business Suite 33: version must be >= 33.3 to be patched.Affected if Installed version falls within the affected ranges listed above - the system is vulnerable.
-
Confirm player handles ARF/WRF filesThis is the default functionality of the Webex Network Recording Player and Webex Player - they are designed to open .arf and .wrf files. Verify the file association or test opening a legitimate recording file.Affected if The player can open ARF or WRF files - the exploitation vector exists if the file comes from an untrusted source.
If a Cisco Webex player is installed with a version below the safe thresholds (1.3.37 for Online, specific builds for Meetings Server, 32.15.10 for Business Suite 32, 33.3 for Business Suite 33), the system is vulnerable to arbitrary code execution via malicious recording 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.3732.15.1033.3
Users should not open ARF or WRF files from untrusted sources. Organizations should deploy available security updates for Cisco Webex players and consider email filtering to block suspicious recording file attachments.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15416 — 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-15416 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