Webex Business SuiteApplication · Cisco
CVE-2019-15284
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 confidenceInsufficient validation of elements in Webex ARF/WRF recording files allows arbitrary code execution when a user opens a malicious recording file. The vulnerability is in the file parsing logic of Cisco Webex Network Recording Player and Webex Player for Windows, requiring user interaction to trigger.
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 Business SuiteApplication
< 39.5.12
Webex Meetings OnlineApplication
< 1.3.44
Webex Meetings ServerApplication
= 3.0mr2= 4.0= t39.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.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 installed Webex Network Recording Player versionOpen Windows Control Panel > Programs and Features, locate 'Cisco Webex Network Recording Player' or 'Webex Player', and note the version column. Alternatively, run 'wmic product get name,version' from command prompt.Affected if The installed version is less than 39.5.12 for Webex Business Suite, less than 1.3.44 for Webex Meetings Online, or exactly 3.0mr2, 4.0, or t39.3 for Webex Meetings Server
-
Confirm Webex player executable existsNavigate to typical installation paths such as C:\Program Files\Cisco Systems\ or C:\Program Files (x86)\Cisco Systems\ and verify the presence of executables like atgavp.exe, wbxcod64.dll, or the WebexPlayer.exe file.Affected if The player binaries exist and the version cannot be determined or falls within the affected ranges
-
Verify file association for ARF/WRF filesCheck Windows registry under HKCR\.arf, HKCR\.wrf, or HKLM\SOFTWARE\Classes\ to confirm file type associations point to the vulnerable Webex player components.Affected if ARF or WRF file associations exist and point to an unpatched Webex player version
-
Check recent Webex recording file accessReview Windows event logs under Security or Application logs for recent access to .arf or .wrf files, or check the user's recent documents folder for any opened Webex recording files.Affected if ARF/WRF files have been opened with a vulnerable player version
A user is affected if the Cisco Webex Network Recording Player or Webex Player for Windows is installed with a version less than 39.5.12, less than 1.3.44, or exactly 3.0mr2, 4.0, or t39.3, and the system handles ARF/WRF 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 Cisco's available patches for Webex players. Avoid opening untrusted or unexpected ARF/WRF files received via email or links.
Fix this in Webex Business Suite
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15284 — 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-15284 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