Webex Meetings ServerApplication · Cisco
CVE-2017-12372
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 "Cisco WebEx Network Recording Player Remote Code Execution Vulnerability" exists in Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) and WebEx Recording Format (WRF) files. A remote attacker could exploit this by providing a user with a malicious ARF or WRF file via email or URL and convincing the user to launch the file. Exploitation of this could cause an affected player to crash and, in some cases, could allow arbitrary code execution on the system of a targeted user. Cisco Bug IDs: CSCvf57234, CSCvg54868, CSCvg54870.
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 remote code execution vulnerability exists in Cisco WebEx Network Recording Player when processing malicious Advanced Recording Format (ARF) or WebEx Recording Format (WRF) files. Attackers deliver specially crafted files via email or URLs, and when users open these files, the player crashes and may execute arbitrary code on the targeted 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 ServerApplication
= 2.6= 2.7
Webex MeetingsApplication
= t29= t30= t31.11.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 Network Recording Player is installedOn Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty' on the player executable in the WebEx installation directory. On macOS, check /Applications for WebEx folder.Affected if The program is found in the system
-
Locate the WebEx Network Recording Player executableCommon paths include C:\Program Files\WebEx\WebEx Recording Player\ or check the version file within the WebEx installation folder. Look for files named nbrplay.exe or similar.Affected if The player executable exists on the system
-
Determine the installed player versionRight-click the player executable, select Properties, then view the Details tab for version information. Alternatively, run 'wmic product get name,version' or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for WebEx entries.Affected if A version number is retrieved from the player or its installer
-
Compare your version against affected releasesMatch the installed version against Cisco Webex Meetings Server versions 2.6 or 2.7, and Cisco Webex Meetings versions t29, t30, or t31.11.2. Note that the player version may differ from the meeting server version.Affected if The installed version matches exactly 2.6 or 2.7 (Webex Meetings Server) OR t29, t30, or t31.11.2 (Webex Meetings)
-
Verify if the system processes ARF or WRF filesCheck recent file access logs or search for .arf and .wrf file extensions in user directories to see if the player has been used to open recording files.Affected if ARF or WRF files have been opened with the WebEx player
The system is affected if Cisco WebEx Network Recording Player is installed and the associated WebEx Meetings Server or Meetings version matches 2.6, 2.7, t29, t30, or t31.11.2.
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 ARF or WRF files; organizations should deploy Cisco's patches for the WebEx Network Recording Player across all affected endpoints and implement endpoint protection controls.
Fix this in Webex Meetings Server
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-2017-12372 — 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-2017-12372 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