Webex Business SuiteApplication · Cisco
CVE-2019-1929
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 because the affected software improperly validates Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. 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 confidenceVulnerabilities in Cisco Webex Network Recording Player and Cisco Webex Player for Windows allow arbitrary code execution due to improper validation of ARF and WRF recording files. Attackers deliver malicious recording files via links or email attachments; when opened with the affected player, 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 Business SuiteApplication
< 39.5.5
Webex Meetings OnlineApplication
< 1.3.43
Webex Meetings ServerApplication
= 2.8= 3.0= 3.0mr2= 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.
-
Confirm Webex player installationCheck for installed Cisco Webex recording player software. On Windows, look in Program Files for 'Webex' or 'Cisco' folders, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Webex-related entries. The player may appear as 'Cisco Webex Network Recording Player' or 'Cisco Webex Player'.Affected if The player is not installed on the system.
-
Identify the installed versionLocate the player's executable (typically in the Webex installation directory, commonly C:\Program Files\Webex\Webex Recording Player or similar). Right-click the executable, select Properties, and view the Details tab for version information. Alternatively, right-click the .exe file in Windows Explorer and select 'Properties' > 'File version'.Affected if The version cannot be determined or is lower than the patched releases.
-
Compare version to affected rangesMatch your installed version against: Cisco Webex Business Suite versions before 39.5.5; Cisco Webex Meetings Online versions before 1.3.43; Cisco Webex Meetings Server versions 2.8, 3.0, 3.0mr2, or 4.0. Note that version comparison should account for full version strings (e.g., 39.5.4 would be vulnerable, 39.5.5 or higher would be fixed).Affected if The installed version falls within any of the vulnerable version ranges listed.
-
Check ARF/WRF file associationsOpen Windows Explorer, navigate to a folder containing an ARF or WRF file (or create a test file with .arf or .wrf extension). Right-click the file, select 'Properties', then 'Opens with' to see which player is associated. Also check Default Programs in Control Panel to see if Webex player is registered as the handler for these file types.Affected if Webex Player is the default handler for .arf or .wrf files and the player version is vulnerable.
-
Verify player executable pathSearch for files named '*.exe' containing 'webex' and 'player' in Program Files directories (C:\Program Files\Webex, C:\Program Files\Cisco). Common executables include atgcnv.exe, webex.exe, or similar. Confirm the exact executable associated with your installation.Affected if The player executable exists and corresponds to a vulnerable version.
A user is affected if Cisco Webex Network Recording Player or Webex Player for Windows is installed with a version matching the vulnerable ranges (less than 39.5.5 for Webex Business Suite, less than 1.3.43 for Webex Meetings Online, or exactly 2.8/3.0/3.0mr2/4.0 for Webex Meetings Server) and the system can open ARF/WRF files with that player.
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.4339.5.5
Deploy the vendor-supplied security update from Cisco to resolve the improper file validation in the Webex players. Until patched, advise users not to open untrusted ARF/WRF files.
Fix this in Webex Business Suite
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1929 — 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-1929 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