Webex MeetingsApplication · Cisco
CVE-2020-3128
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 are due to insufficient validation of certain elements within a Webex recording that is stored in either the Advanced Recording Format (ARF) or the Webex Recording Format (WRF). An attacker could exploit these vulnerabilities by sending a malicious ARF or WRF file to a user through a link or email attachment and persuading the user to open the file 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 stem from insufficient validation of certain elements within Webex recordings stored in ARF or WRF format. An attacker can craft a malicious recording file and trick a user into opening it, achieving arbitrary code execution with the victim'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 MeetingsApplication
>= 39.5, < 39.5.17
Webex Meetings OnlineApplication
< 1.3.49
Webex Meetings ServerApplication
< 3.0= 3.0= 4.0
Webex Network Recording PlayerApplication
< 39.5.17< 39.11.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.
-
Identify if Cisco Webex Player is installedOpen Windows Settings > Apps > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs containing 'Webex Player' or 'Webex Network Recording Player'Affected if The product appears in the installed programs list
-
Determine the exact version of Cisco Webex Network Recording PlayerRun 'Get-ItemProperty "C:\Program Files\Webex\Webex Network Recording Player\WebexNrp.dll" -ErrorAction SilentlyContinue | Select-Object VersionInfo' or right-click the DLL and select Properties > Details to view the File VersionAffected if The version shown is less than 39.5.17 or less than 39.11.0 (depending on the product line)
-
Determine the exact version of Cisco Webex Meetings ClientRun 'Get-ItemProperty "C:\Program Files\Webex\Webex Meetings\atlgui.exe" -ErrorAction SilentlyContinue | Select-Object VersionInfo' or check the installed programs list for the full version numberAffected if The version shown is 39.5.x where x is less than 17, or is less than 1.3.49 for Webex Meetings Online, or is 3.0.x or 4.0.x for Webex Meetings Server
-
Confirm the player can process ARF or WRF recording filesCheck if the Webex Network Recording Player executable exists at 'C:\Program Files\Webex\Webex Network Recording Player\WebexNrp.exe' or 'C:\Program Files\Webex\Webex Player\WebexPlayer.exe'Affected if The player executable exists and the system can open .arf or .wrf files (vulnerability requires this component to be present and functional)
You are affected if Cisco Webex Player or Cisco Webex Network Recording Player is installed with a version number that falls within any of the affected ranges: < 39.5.17, < 39.11.0, < 1.3.49, or version 3.0.x / 4.0.x for Webex Meetings Server.
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.493.039.5.17
Organizations should deploy vendor-provided patches for Cisco Webex Player when available, and users should avoid opening untrusted Webex recording files from unknown sources.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3128 — 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-2020-3128 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