dbcve.org
Webex MeetingsApplication · Cisco

CVE-2017-12369

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 Out-of-Bounds 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: CSCve30208, CSCve30214, CSCve30268.

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

An out-of-bounds memory vulnerability exists in Cisco WebEx Network Recording Player when parsing malicious Advanced Recording Format (ARF) or WebEx Recording Format (WRF) files. A remote attacker can deliver a crafted file via email or URL and convince the user to open it, triggering the vulnerability which can cause a crash or allow arbitrary code execution on the targeted user's system.

MitigationUsers should not open untrusted ARF or WRF files received via email or URLs; organizations should apply Cisco's available patches for the WebEx player and implement email/URL filtering to block suspicious recording files.

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:= t29= t30= t31= t32

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. Locate Cisco WebEx Network Recording Player installation
    Search for 'WebEx Network Recording Player' or 'WebExNBRPlayer' in program directories (typically C:\Program Files\Cisco Systems\ on Windows or /Applications on macOS). Also check Add/Remove Programs or system registry for installed Cisco WebEx components.
    Affected if The player application is found on the system
  2. Identify installed WebEx player version
    Right-click the executable (often named WebExNBRPlayer.exe or similar), select Properties, and view the Version tab. Alternatively, open the player, go to Help > About. Note the full version string.
    Affected if Version matches t29, t30, t31, or t32 exactly
  3. Verify file association with ARF/WRF extensions
    Check if .arf and .wrf file extensions are associated with the WebEx Network Recording Player. Look in Windows Explorer > Tools > Folder Options > File Types, or inspect registry keys under HKEY_CLASSES_ROOT for .arf and .wrf entries.
    Affected if ARF/WRF file types are registered to open with the WebEx player
  4. Confirm player can parse recording files
    Attempt to open any existing ARF or WRF file, or check if the player has rendering/parsing functionality enabled. The vulnerability triggers during file parsing operations.
    Affected if The player can parse ARF or WRF files and the version is t29-t32

A user is affected if Cisco WebEx Network Recording Player version t29, t30, t31, or t32 is installed and capable of opening ARF or WRF 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should not open untrusted ARF or WRF files received via email or URLs; organizations should apply Cisco's available patches for the WebEx player and implement email/URL filtering to block suspicious recording files.

Recommended fix Moderate confidence

Latest Cisco WebEx Network Recording Player / Webex Meetings version (post-T32) that includes fixes for CSCve30208, CSCve30214, CSCve30268

  1. 1. Identify the current version of Cisco WebEx Network Recording Player installed on affected systems by opening the player and checking Help > About, or checking the installed programs list in Control Panel.
  2. 2. Navigate to the official Cisco Software Download center at software.cisco.com and search for 'WebEx Network Recording Player' or 'Webex Meetings' updates.
  3. 3. Download the latest available version of Cisco WebEx Network Recording Player that addresses security vulnerabilities.
  4. 4. Uninstall the current version of WebEx Network Recording Player from all affected systems via Control Panel > Programs and Features.
  5. 5. Install the newly downloaded updated version of the WebEx Network Recording Player.
  6. 6. Verify the installation was successful by checking the version number matches the downloaded update.
  7. 7. Alternatively, ensure WebEx Meetings client is updated to the latest version through the application's automatic update feature or by reinstalling the current version which will trigger an update check.
Caveat Standard upgrade risk - ensure compatibility with existing meeting infrastructure and test recordings playback before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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