Webex MeetingsApplication · Cisco
CVE-2017-12368
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: CSCve10584, CSCve10591, CSCve11503, CSCve10658, CSCve11507, CSCve10749, CSCve10744, CSCve11532, CSCve10762, CSCve10764, CSCve11538.
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 can be exploited to execute arbitrary code on the targeted user's 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 MeetingsApplication
= t29= t30= t31= t32
Webex Meetings ServerApplication
= 2.6= 2.7CVSS 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 Cisco WebEx Network Recording Player installationCheck for the presence of the player by looking for 'WebEx Network Recording Player' in installed programs on Windows (Registry: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or by locating common installation paths such as C:\Program Files\WebEx\ or C:\Users\[user]\AppData\Local\WebEx\Affected if The player is installed on the system
-
Determine installed WebEx Meetings versionOpen the WebEx desktop application and navigate to Help > About WebEx Meetings, or check the Windows registry at HKLM\SOFTWARE\Cisco\WebEx\Meetings\Install for the Version valueAffected if The version matches t29, t30, t31, or t32
-
Determine installed WebEx Meetings Server versionIf using on-premises WebEx Meetings Server, log into the administration console and navigate to Configuration > Server Information to view the versionAffected if The version matches 2.6 or 2.7
-
Inspect recently opened ARF or WRF filesCheck the user's recent documents folder or email attachments for .arf and .wrf files, and review browser download history or email client attachment logs for these file typesAffected if Any untrusted or unexpected ARF/WRF files were recently opened by the user
-
Review application crash logs for WebEx playerCheck Windows Event Viewer under Windows Logs > Application for crash events from 'WebEx Network Recording Player' or 'atucfplta.dll' occurring around the time of suspicious file openingAffected if Recent crashes of the Network Recording Player are logged
A user is affected if Cisco WebEx Network Recording Player is installed and the WebEx Meetings version is t29, t30, t31, t32, or the WebEx Meetings Server version is 2.6 or 2.7, especially if untrusted ARF/WRF files have been opened.
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 dataUpdate to patched versions of Cisco WebEx Network Recording Player and implement controls to prevent users from opening untrusted ARF/WRF files from unknown sources.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12368 — 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-12368 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