CVE-2018-0103
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 a local attacker to execute arbitrary code on the system of a user. The attacker could exploit this vulnerability by sending the user a link or email attachment with a malicious ARF file and persuading the user to follow the link or launch the file. Successful exploitation could allow the attacker to execute arbitrary code on the user's system. 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: CSCvg78835, CSCvg78837, CSCvg78839.
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 processing maliciously crafted Advanced Recording Format (ARF) files. Successful exploitation allows arbitrary code execution on the victim's system through a specially designed ARF file delivered via link or email attachment.
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 dataall versionsall versionsall versionsall versionsCVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Cisco WebEx Network Recording Player is installedCheck for the player installation on Windows: look for 'Webex Network Recording Player' or 'Cisco WebEx' in Add/Remove Programs, Program Files, or check for the executable (typically atpplay.exe or similar WebEx player binaries). On Mac, check /Applications for WebEx-related packages.Affected if The Network Recording Player component is present on the system.
-
Verify ARF file handling capabilityCheck if .arf file extension is associated with the WebEx player. Look in Windows Registry under HKCR\.arf or check file associations, or on Mac check ~/Library/Application Support/WebEx for ARF-related components.Affected if The system has .arf file associations configured for the WebEx player.
-
Check installed WebEx player versionRight-click the player executable, select Properties, then Details to view version information. Alternatively, open the WebEx player and look in Help > About. For Windows installations, also check the Windows installer entry in Add/Remove Programs for version details.Affected if Any version of the Cisco WebEx Network Recording Player is found, since all versions are affected per the advisory.
-
Check for presence of related WebEx client softwareSearch for WebEx client installations: look for 'Cisco WebEx Meeting Manager', 'Webex' in installed programs, or check for process executables (atcli.exe, webex.exe, webexmta.exe) in system processes or Program Files.Affected if Any Cisco WebEx client software (Business Suite, Meetings, Meetings Server) with Network Recording Player functionality is installed.
The environment is affected if Cisco WebEx Network Recording Player or any associated WebEx client with ARF playback capability is installed, regardless of version, since all versions are listed as vulnerable.
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 dataUsers should not open ARF files from untrusted sources. Organizations should apply Cisco's patches for affected WebEx products and implement email filtering/user awareness training to mitigate social engineering vectors.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0103 — 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-2018-0103 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