Webex Meetings OnlineApplication · Cisco
CVE-2019-1638
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. Successful exploitation 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 Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. Attackers exploit this by sending malicious ARF or WRF files that, when opened by users, execute arbitrary code 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 Meetings OnlineApplication
= 1.3.33= 1.3.39= t32.9= t33.3.5= t33.5.1
Webex Meetings ServerApplication
= 3.0mr2= t31CVSS 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.
-
Confirm Webex Player installationCheck for Cisco Webex Network Recording Player or Cisco Webex Player on Windows. Look in Program Files for 'Webex' folder or check Programs and Features (Add/Remove Programs) for Webex-related entries.Affected if Either Cisco Webex Network Recording Player or Cisco Webex Player for Windows is installed.
-
Identify installed version via file propertiesLocate the player executable (typically in C:\Program Files\Webex\Webex Recording Player or similar). Right-click the .exe file, select Properties, and check the Version tab for the product version.Affected if The version matches one of the affected versions: 1.3.33, 1.3.39, t32.9, t33.3.5, t33.5.1 (for Webex Meetings Online) or 3.0mr2, t31 (for Webex Meetings Server).
-
Identify version via command lineOpen Command Prompt and run: wmic product where "name like '%Webex%'" get name,version. Alternatively, check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Webex entries.Affected if The returned version matches the affected versions listed above.
-
Check for ARF/WRF file associationThe vulnerable functionality is handling ARF and WRF recording files. These file extensions (.arf, .wrf) are associated with the Webex Player by default when the player is installed. No additional configuration check is needed as this is the core purpose of the player.Affected if The Webex Player is installed and capable of opening .arf or .wrf files, which is the default state after installation.
A system is affected if Cisco Webex Network Recording Player or Cisco Webex Player for Windows is installed and the installed version matches one of the affected versions (1.3.33, 1.3.39, t32.9, t33.3.5, t33.5.1, 3.0mr2, or t31).
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 dataUsers should not open untrusted or unexpected ARF/WRF files received via email or links. Organizations should deploy the Cisco software update/patch when available and ensure Webex players are updated to the patched version.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1638 — 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-1638 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