dbcve.org
Webex Advanced Recording Format PlayerApplication · Cisco

CVE-2017-6669

HIGH · 7.8 CVSS v3.1 Published 2017-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Multiple buffer overflow vulnerabilities exist in the Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) files. An attacker could exploit these vulnerabilities by providing a user with a malicious ARF file via email or URL and convincing the user to launch the file. Exploitation of these vulnerabilities could cause an affected player to crash and, in some cases, could allow arbitrary code execution on the system of a targeted user. The Cisco WebEx Network Recording Player is an application that is used to play back WebEx meeting recordings that have been recorded on the computer of an online meeting attendee. The player can be automatically installed when the user accesses a recording file that is hosted on a WebEx server. The following client builds are affected by this vulnerability: Cisco WebEx Business Suite (WBS29) client builds prior to T29.13.130, Cisco WebEx Business Suite (WBS30) client builds prior to T30.17, Cisco WebEx Business Suite (WBS31) client builds prior to T31.10. Cisco Bug IDs: CSCvc47758 CSCvc51227 CSCvc51242.

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

Buffer overflow vulnerabilities in Cisco WebEx Network Recording Player when parsing maliciously crafted ARF (Advanced Recording Format) files. An attacker tricks a user into opening a specially crafted ARF file, causing the player to crash and potentially execute arbitrary code with the user's privileges.

MitigationApply vendor patches by upgrading Cisco WebEx client builds to T29.13.130 or later for WBS29, T30.17 or later for WBS30, and T31.10 or later for WBS31. Additionally, enforce user awareness to avoid opening untrusted ARF files from unknown sources.

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 Advanced Recording Format PlayerApplication
Affected:= 29.10

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
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 checks

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

  1. Verify Cisco WebEx ARF Player is installed
    Check for the presence of the WebEx Advanced Recording Format Player on the system. Common installation paths include C:\Program Files\WebEx\WebEx Recording Player or C:\Program Files (x86)\WebEx\WebEx Recording Player. On Windows, check Add/Remove Programs or the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries named 'WebEx Recording Player' or similar.
    Affected if The Cisco WebEx ARF Player software is found on the system.
  2. Determine the installed ARF Player version
    Locate the WebEx Recording Player executable (wrw.exe or similar) and check its file properties, or run a command to retrieve version info. On Windows, right-click the executable and select Properties, then view the Details tab for Product Version. Alternatively, use the command: dir "C:\Program Files\WebEx\WebEx Recording Player\*.*" /s or inspect the version resource using a tool like strings or a PE viewer.
    Affected if The version displayed is 29.10 or earlier versions within the WBS29 branch.
  3. Confirm ARF file handling capability is present
    Verify the player component can process ARF files by checking for the presence of ARF-related DLLs or processing modules within the WebEx installation directory. The vulnerability triggers specifically when the player parses ARF files, so the player component must be functional and capable of opening these files.
    Affected if The ARF Player component exists and can process ARF files.
  4. Identify if the system has been used to open ARF files
    Review recent file access logs, browser download history, or the user's recent documents folder for any .arf file downloads or openings. Check Windows Event Logs under Security or Application logs for events indicating WebEx player execution with ARF file arguments. Use the command: wevtutil qe Security /c:10 /f:text /q:"*[System[(EventID=4688) and Provider[@Name='Microsoft-Windows-Security-Auditing'] and (EventData[@Name='ProcessName']='C:\\Program Files\\WebEx\\WebEx Recording Player\\wrw.exe')]]]"
    Affected if There is evidence that the system was used to open ARF files, which would trigger the vulnerable code path.

A user is affected if Cisco WebEx ARF Player version 29.10 (or earlier WBS29 versions) is installed and the system is used to open ARF files, allowing the specially crafted ARF to trigger the buffer overflow.

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 by upgrading Cisco WebEx client builds to T29.13.130 or later for WBS29, T30.17 or later for WBS30, and T31.10 or later for WBS31. Additionally, enforce user awareness to avoid opening untrusted ARF files from unknown sources.

Fix this in Webex Advanced Recording Format Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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