Webex Business SuiteApplication · Cisco

CVE-2019-1927

HIGH · 7.8 CVSS v3.1 Published 2019-08-07
Fix available
A fix is available. Upgrade to 1.3.43 / 39.5.5 or later.
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
Multiple 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 confidence

The vulnerability exists in Cisco Webex Network Recording Player and Webex Player for Windows due to improper validation of Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. Attackers can craft malicious recording files that, when opened by a user, allow arbitrary code execution with the user's privileges.

MitigationApply the vendor patch from Cisco to update Webex Network Recording Player and Webex Player to a fixed version. Additionally, train users to avoid opening untrusted recording files from unknown sources.

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
Affected:< 39.5.5
Webex Meetings OnlineApplication
Affected:< 1.3.43
Webex Meetings ServerApplication
Affected:= 2.8= 3.0= 3.0mr2= 4.0

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 checks

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

  1. Identify installed Webex player software
    Locate Cisco Webex Network Recording Player or Webex Player on the Windows system (typically in Program Files). Note the exact product name displayed.
    Affected if Neither Webex Network Recording Player nor Webex Player is installed, then the system is not affected.
  2. Check Webex Business Suite version
    Determine the installed version of Cisco Webex Business Suite (if applicable). Compare against the affected range: versions less than 39.5.5.
    Affected if The installed version is Cisco Webex Business Suite and is less than 39.5.5.
  3. Check Webex Meetings Online version
    Determine the installed version of Cisco Webex Meetings Online (if applicable). Compare against the affected range: versions less than 1.3.43.
    Affected if The installed version is Cisco Webex Meetings Online and is less than 1.3.43.
  4. Check Webex Meetings Server version
    Determine the installed version of Cisco Webex Meetings Server (if applicable). Compare against the affected versions: 2.8, 3.0, 3.0mr2, or 4.0.
    Affected if The installed version is Cisco Webex Meetings Server and matches exactly 2.8, 3.0, 3.0mr2, or 4.0.

The system is affected if Webex Network Recording Player or Webex Player for Windows is installed and the version matches one of the affected ranges: Webex Business Suite < 39.5.5, Webex Meetings Online < 1.3.43, or Webex Meetings Server version 2.8, 3.0, 3.0mr2, or 4.0.

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
Upgrade available Upgrade to 1.3.43 / 39.5.5 or later
Fixed in 1.3.4339.5.5
Interim mitigation

Apply the vendor patch from Cisco to update Webex Network Recording Player and Webex Player to a fixed version. Additionally, train users to avoid opening untrusted recording files from unknown sources.

Fix this in Webex Business Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1927 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1927 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