Webex MeetingsApplication · Cisco
CVE-2020-3127
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 · moderate confidenceVulnerability in Cisco Webex Network Recording Player and Webex Player for Windows due to insufficient validation of elements within ARF or WRF recording files. An attacker can craft a malicious recording file that, when opened by a user, allows arbitrary code execution 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 MeetingsApplication
>= 39.5, < 39.5.17
Webex Meetings OnlineApplication
< 1.3.43
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 & features, or use 'appwiz.cpl' to list installed programs. Look for 'Cisco Webex Network Recording Player', 'Cisco Webex Player', or 'Cisco Webex Meetings' in the installed applications list.Affected if The application is present on the system
-
Determine the installed Webex Player versionIf found, click on the application in Apps & features to view the version, or navigate to the Webex installation directory (commonly in Program Files/Cisco Systems) and locate the player executable. Right-click the executable, select Properties, and check the Details tab for the Product Version.Affected if The version displayed is lower than 39.5.17 (for versions 39.5 and above), lower than 1.3.43 (for Webex Meetings Online), or the product is Webex Meetings Server versions 3.0 or 4.0, or any version prior to 3.0
-
Confirm the player handles ARF or WRF file typesAttempt to open an ARF or WRF recording file with the installed Webex Player, or check file type associations in Windows Settings > Apps > Default apps > Choose default apps by file type to see if .arf or .wrf files are associated with the Webex Player.Affected if ARF or WRF files are associated with and openable by the Cisco Webex Player, meaning the vulnerable component is actively in use
-
Check for recent security updates to the playerOpen the Webex Player and look in Help > About, or check the Cisco Webex download site for the latest version number. Compare your installed version against the patched releases (39.5.17 or higher, or 39.11.0 or higher for Network Recording Player).Affected if The installed version has not been updated to the patched versions and matches the affected ranges listed
A user is affected if the Cisco Webex Network Recording Player or Webex Player for Windows is installed with a version that falls within the affected ranges (39.5 to <39.5.17, <1.3.43 for Meetings Online, or versions 3.0/4.0 for Meetings Server) and the player is capable of opening ARF or WRF recording files.
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.433.039.5.17
Do not open untrusted or unexpected Webex recording files (ARF/WRF). Update to the patched Cisco Webex player version. Use endpoint protection and email filtering to block malicious file attachments.
Fix this in Webex Meetings
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-2020-3127 — 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-3127 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