Webex Meeting CenterApplication · Cisco
CVE-2017-12359
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 Buffer Overflow vulnerability in Cisco WebEx Network Recording Player for Advanced Recording Format (.arf) files could allow an attacker to execute arbitrary code on a system. An attacker could exploit this vulnerability by providing a user with a malicious .arf file via email or URL and convincing the user to launch the file. Exploitation of this vulnerability could allow arbitrary code execution on the system of the targeted user. This vulnerability affects Cisco WebEx Business Suite meeting sites, Cisco WebEx Meetings sites, Cisco WebEx Meetings Server, and Cisco WebEx ARF players. Cisco Bug IDs: CSCve10729, CSCve10771, CSCve10779, CSCve11521, CSCve11543.
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 confidenceBuffer overflow vulnerability in Cisco WebEx Network Recording Player when parsing maliciously crafted .arf (Advanced Recording Format) files. Successful exploitation allows arbitrary code execution on the targeted user's system. Attack requires user interaction to open the malicious file delivered via email or URL.
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 Meeting CenterApplication
= t29= t30= t31= t32
Webex Meetings ServerApplication
= 2.6.0= 2.7.0CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 WebEx Network Recording Player application on the system. Look for executable files such as 'atgplayer.exe' or 'webexplayer.exe' in typical installation directories like C:\Program Files\Cisco Systems\WebEx\ or C:\Program Files (x86)\Cisco Systems\WebEx\Affected if The application is installed and the version matches the affected product versions below
-
Check Cisco WebEx Meeting Center versionOpen the WebEx Meeting Center application or check its About/Help section to locate the exact version number. Compare against the affected versions: t29, t30, t31, t32Affected if The installed version is exactly t29, t30, t31, or t32
-
Check Cisco WebEx Meetings Server versionAccess the WebEx Meetings Server administration console or check the server's version information. Compare against the affected versions: 2.6.0 and 2.7.0Affected if The installed version is exactly 2.6.0 or 2.7.0
-
Confirm .arf file handling capabilityVerify that the WebEx Network Recording Player can process .arf (Advanced Recording Format) files by checking file associations or attempting to view a legitimate .arf recording if availableAffected if The player can process .arf files, meaning the parsing vulnerable component is present and accessible
A user is affected if Cisco WebEx Network Recording Player is installed with WebEx Meeting Center version t29, t30, t31, or t32, or WebEx Meetings Server version 2.6.0 or 2.7, and the system can open .arf files.
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 dataApply vendor-provided patches/updates for affected Cisco WebEx products. Users should avoid opening untrusted .arf files from unknown sources.
Fix this in Webex Meeting Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12359 — 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-12359 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