Webex Business SuiteApplication · Cisco
CVE-2019-1772
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 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.
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 in Cisco Webex Network Recording Player and Cisco Webex Player for Windows allows arbitrary code execution due to improper validation of ARF and WRF recording files. An attacker can craft a malicious recording file that, when opened by a user, enables 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 Business SuiteApplication
< 39.1.0.471
Webex Business Suite LockdownApplication
< 33.6.11
Webex Meetings OnlineApplication
< 1.3.42
Webex Meetings ServerApplication
= 2.8\(1\)= 3.0\(1\)CVSS 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.
-
Check if Cisco Webex Player is installedLook for Webex Network Recording Player or Webex Player in the list of installed programs (Control Panel > Programs and Features) or check for the executable files (typically in C:\Program Files\Webex\Webex Player or similar locations)Affected if The player software is present on the system
-
Identify the installed version of Cisco Webex PlayerRight-click on the Webex Player executable (often named 'WebexPlayer.exe' or similar), select Properties, and check the Version tab. Alternatively, open the player and look in Help > AboutAffected if The version number is lower than 39.1.0.471 for standard Business Suite, lower than 33.6.11 for Lockdown version, lower than 1.3.42 for Meetings Online, or exactly 2.8(1) or 3.0(1) for Meetings Server
-
Verify file type association for .arf and .wrf filesOpen a command prompt and run 'assoc .arf' and 'assoc .wrf' to see which application is registered to open these file types. Alternatively, check default file associations in Windows Settings > Apps > Default AppsAffected if The .arf or .wrf file extensions are associated with the Cisco Webex Player application and the player version is vulnerable
-
Inspect recent ARF/WRF files in common download locationsCheck user directories for recently downloaded or received .arf and .wrf files: %UserProfile%\Downloads, %UserProfile%\Desktop, and email attachment foldersAffected if There are .arf or .wrf files present that originated from untrusted or unexpected sources
-
Check for Webex-related processes handling recording filesUse Task Manager or process monitoring tools to observe if WebexPlayer.exe is actively processing recording files, particularly from temporary or download directoriesAffected if The player is actively opening files from untrusted locations
-
Review software inventory for Webex Meetings Server versionIf using an on-premise Cisco Webex Meetings Server, check the admin interface or system documentation for the deployed version numberAffected if The server version is exactly 2.8(1) or 3.0(1)
A user is affected if Cisco Webex Player or Cisco Webex Meetings Server with a vulnerable version is installed and is configured to handle ARF/WRF recording files, combined with the risk of opening untrusted 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.4233.6.1139.1.0.471
Users should not open untrusted or unexpected ARF/WRF files received via email or links. Organizations should update to patched versions of Cisco Webex players and consider endpoint detection tools to monitor for suspicious file handling.
Fix this in Webex Business Suite
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1772 — 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-1772 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