Webex MeetingsApplication · Cisco
CVE-2017-12370
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: CSCvf38060, CSCvg54836, CSCvf38077, CSCvg54843, CSCvf38084, CSCvg54850.
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 confidenceThis is a client-side remote code execution vulnerability in Cisco WebEx Network Recording Player that handles ARF and WRF recording files. An attacker can craft a malicious recording file and deliver it via email or URL; when the victim opens the file, the player's flawed parsing logic can be exploited to execute arbitrary code on the target system, potentially with the user's privileges.
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
= t30= t31CVSS 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.
-
Verify WebEx Network Recording Player is installedCheck for the presence of the player on the system. On Windows, look for installation directories under Program Files or check registry keys under HKLM\SOFTWARE\Cisco Systems. On Mac, check /Applications for WebEx components.Affected if The player software is found on the system
-
Identify installed WebEx client versionRun 'msiexec /x {product-code}' or check Add/Remove Programs for the version entry. The version typically displays as t30, t31, or similar in the version string.Affected if The installed version matches t30 or t31 (the affected versions listed)
-
Confirm player handles ARF and WRF file typesVerify the player is configured to process .arf and .wrf file extensions. Check file association settings in Windows or examine the player's supported formats documentation.Affected if The player is associated with or capable of opening ARF/WRF files (default player behavior)
-
Determine if untrusted recording files can be openedReview whether email attachment filtering or endpoint controls are in place to block untrusted ARF/WRF files. Check browser/download folder security settings.Affected if Users can directly open ARF/WRF files from email or downloads without additional controls
The environment is affected if Cisco WebEx Network Recording Player version t30 or t31 is installed and users can open ARF/WRF recording files, as the vulnerable parsing code executes upon file access.
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 dataOrganizations should ensure all WebEx clients are updated to the latest patched version once Cisco releases updates, and users should be instructed to never open untrusted ARF or WRF files received via email or from untrusted sources.
Fix this in Webex Meetings
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-12370 — 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-12370 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