Webex MeetingsApplication · Cisco
CVE-2019-15285
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 · uneditedMultiple vulnerabilities in Cisco Webex Network Recording Player for Microsoft Windows and Cisco Webex Player for Microsoft Windows could allow an attacker to execute arbitrary code on an affected system. The vulnerabilities exist due to insufficient validation of certain elements with a Webex recording stored in either the Advanced Recording Format (ARF) or the Webex Recording Format (WRF). An attacker could exploit these vulnerabilities by sending a user a malicious ARF or WRF file through a link or email attachment and persuading the user to open the file with the affected software on the local system. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of the targeted user.
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 confidenceMultiple vulnerabilities in Cisco Webex Network Recording Player and Cisco Webex Player for Windows allow arbitrary code execution due to insufficient validation of elements within ARF or WRF recording files. An attacker can embed malicious content in these recording file formats, and when a user opens the file, arbitrary code executes 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 MeetingsApplication
>= 39.5.0, < 39.5.12
Webex Meetings OnlineApplication
< 1.3.44= 32.11= 39.4.0= t32.9= t39.3= t39.6.0
Webex Meetings ServerApplication
= 3.0= 4.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.
-
Identify if Cisco Webex Player is installedCheck for Webex Network Recording Player or Webex Player in installed programs. On Windows, this can be done via Control Panel > Programs and Features, or by querying the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Webex Player' or 'Webex Network Recording Player'.Affected if The software is not found in the system, the user is not affected by this specific player vulnerability.
-
Determine the installed Webex Player versionLocate the player executable (typically named arfPlayer.exe, wrfPlayer.exe, or WebexPlayer.exe within the Cisco Webex installation directory) and check its file properties, or use the command 'wmic product get name,version' if available, or query the version from the uninstall registry key found in the previous step.Affected if Unable to determine version, treat as potentially affected.
-
Compare installed version against affected rangesFor Cisco Webex Meetings, check if version is >= 39.5.0 AND < 39.5.12. For Cisco Webex Meetings Online, check if version matches: < 1.3.44, or equals 32.11, 39.4.0, t32.9, t39.3, or t39.6.0. For Cisco Webex Meetings Server, check if version equals 3.0 or 4.0.Affected if The installed version falls within any of these affected ranges, indicating the system is vulnerable.
-
Verify ARF/WRF file association with Webex PlayerCheck if .arf or .wrf file extensions are associated with the installed Webex Player. This can be checked via Windows Registry under HKCR\.arf and HKCR\.wrf keys, or by inspecting the default programs settings. The vulnerability is triggered specifically when these recording files are opened.Affected if These file types are associated with a vulnerable Webex Player version, the user is at risk when opening untrusted recording files.
A user is affected if they have a vulnerable Cisco Webex Player version (as per the version ranges) installed and have .arf/.wrf file associations that open with that player, enabling code execution when opening 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.4439.5.12
Apply vendor patches from Cisco for affected Webex player versions. Users should not open untrusted or unexpected ARF/WRF recording files received via email or links.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15285 — 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-2019-15285 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