dbcve.org
Webex Meetings OnlineApplication · Cisco

CVE-2019-1639

HIGH · 7.8 CVSS v3.0 Published 2019-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A 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 confidence

The Cisco Webex Network Recording Player and Webex Player for Windows fail to properly validate Advanced Recording Format (ARF) and Webex Recording Format (WRF) files before processing them. This improper validation allows specially crafted malicious recording files to trigger arbitrary code execution when a user opens the file.

MitigationOrganizations should implement email filtering to block untrusted ARF/WRF attachments, train users to avoid opening recording files from untrusted sources, and ensure Webex players are updated to the latest patched versions.

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
Affected:= 1.3.33= 1.3.39= t32.9= t33.3.5= t33.5.1
Webex Meetings ServerApplication
Affected:= 3.0mr2= t31

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Webex Player is installed
    On Windows, open Programs and Features (or run 'appwiz.cpl') and look for 'Cisco Webex Network Recording Player' or 'Webex Player' in the installed programs list.
    Affected if The program is listed as installed.
  2. Identify the exact version of the installed Webex Player
    Right-click the installed Webex Player entry in Programs and Features, select Properties, and view the Version field. Alternatively, navigate to the installation directory (typically C:\Program Files\Webex\Webex Recording Player or similar) and right-click the executable to view its version properties.
    Affected if The version matches 1.3.33, 1.3.39, t32.9, t33.3.5, t33.5.1, 3.0mr2, or t31.
  3. Check for Cisco Webex Meetings Online or Server version
    If using Cisco Webex Meetings Online, log into the Webex site and navigate to Account settings or About to view the meeting site version. For Cisco Webex Meetings Server, check the administration console or release notes for the deployed version.
    Affected if The meeting site or server version is 1.3.33, 1.3.39, t32.9, t33.3.5, t33.5.1, 3.0mr2, or t31.
  4. Inspect recent ARF/WRF file access
    Check the user's recent documents or temporary download folders (such as %USERPROFILE%\Downloads or %USERPROFILE%\Documents) for .arf or .wrf recording files that may have been opened recently. Review browser download history for these file types.
    Affected if Any .arf or .wrf files were opened by the player on the affected version.

A user is affected if Cisco Webex Network Recording Player or Webex Player is installed and the version matches exactly 1.3.33, 1.3.39, t32.9, t33.3.5, t33.5.1, 3.0mr2, or t31, or if the Webex Meetings Online/Server version matches one of these values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should implement email filtering to block untrusted ARF/WRF attachments, train users to avoid opening recording files from untrusted sources, and ensure Webex players are updated to the latest patched versions.

Fix this in Webex Meetings Online Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1639 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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