dbcve.org
Webex MeetingsApplication · Cisco

CVE-2017-12371

CRITICAL · 9.6 CVSS v3.0 Published 2017-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 "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: CSCvf49650, CSCvg54853, CSCvg54856, CSCvf49697, CSCvg54861, CSCvf49707, CSCvg54867.

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

A remote code execution vulnerability exists in Cisco WebEx Network Recording Player when processing malicious Advanced Recording Format (ARF) and WebEx Recording Format (WRF) files. Attackers deliver specially crafted files via email or URLs and trick users into opening them, potentially allowing arbitrary code execution on the victim's system with the user's privileges.

MitigationApply vendor patches from Cisco for the WebEx Network Recording Player. Additionally, train users to avoid opening recording files from untrusted sources and consider implementing endpoint protection to detect malicious file execution.

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
Affected:= t30= 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
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 checks

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

  1. Identify if Cisco WebEx Network Recording Player is installed
    Check common installation locations: Windows typically installs to C:\Program Files\Cisco Systems\WebEx\WebEx Network Recording Player\ or C:\Program Files (x86)\Cisco Systems\WebEx\WebEx Network Recording Player\. On Mac, check /Applications/WebEx/. Alternatively, search for 'WebEx Network Recording Player' in Add/Remove Programs (Windows) or System Preferences > Extensions (Mac).
    Affected if The player software is found on the system.
  2. Determine the installed version of the Network Recording Player
    Locate the executable (nmrpt.exe on Windows, Network Recording Player.app on Mac) and check its properties for version information. On Windows, right-click the .exe file, select Properties, and view the Details tab. The version may also be displayed when launching the player or in the About dialog accessible from the player menu.
    Affected if Unable to determine version or version cannot be verified.
  3. Compare installed version against affected versions
    Match the identified version string against the affected versions t30 and t31. Note any build numbers, patch levels, or track identifiers (such as 't30' or 't31' appearing in the version string). The exact format may vary (e.g., '30.0.x', '31.0.x', or 't30.x.x').
    Affected if The installed version matches or falls within the t30 or t31 version tracks.
  4. Verify if ARF/WRF file association exists
    Check whether the system has file associations configured for .arf and .wrf extensions pointing to the WebEx Network Recording Player. On Windows, view file associations in Settings > Apps > Default Apps > Choose default apps by file type. Confirm the player is registered as the handler for these file types.
    Affected if The player is set as the default handler for .arf or .wrf files, making the system vulnerable when such files are opened.

The system is affected if Cisco WebEx Network Recording Player is installed and the installed version corresponds to the t30 or t31 version tracks, particularly when the player handles .arf or .wrf recording files.

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

Apply vendor patches from Cisco for the WebEx Network Recording Player. Additionally, train users to avoid opening recording files from untrusted sources and consider implementing endpoint protection to detect malicious file execution.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12371 — 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-2017-12371 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