Webex Meetings OnlineApplication · Cisco
CVE-2018-0288
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 vulnerability in Cisco WebEx Recording Format (WRF) Player could allow an unauthenticated, remote attacker to access sensitive data about the application. An attacker could exploit this vulnerability to gain information to conduct additional reconnaissance attacks. The vulnerability is due to a design flaw in Cisco WRF Player. An attacker could exploit this vulnerability by utilizing a maliciously crafted file that could bypass checks in the code and enable an attacker to read memory from outside the bounds of the mapped file. This vulnerability affects Cisco WebEx Business Suite meeting sites, Cisco WebEx Meetings sites, and Cisco WebEx WRF players. Cisco Bug IDs: CSCvh89107, CSCvh89113, CSCvh89132, CSCvh89142.
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 design flaw in Cisco WebEx Recording Format (WRF) Player allows a maliciously crafted WRF file to bypass security checks, enabling an out-of-bounds memory read that exposes sensitive application information to unauthenticated remote attackers for reconnaissance purposes.
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 Meetings OnlineApplication
= t31.20= t31.20.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 WebEx WRF Player installationCheck for Cisco WebEx installation on the system. Look for WebEx player executables (e.g., GPCMenu.exe, WebEx.exe) or check installed programs list for 'Cisco WebEx' or 'WebEx Recording Format Player'. On Windows, check 'Add or Remove Programs' or the installation directory (commonly C:\Program Files\Cisco Systems\WebEx\ or C:\Program Files\WebEx\).Affected if Cisco WebEx WRF Player is installed on the system
-
Determine WebEx player versionOpen the WebEx player or right-click a .wrf file to view properties. Alternatively, check the WebEx installation directory for version information files, or open WebEx Meeting Center and check the version info through Help > About. Compare the version number to t31.20 or t31.20.2.Affected if The installed WebEx version is exactly t31.20 or t31.20.2
-
Check if WRF file association is enabledVerify that .wrf file type is associated with the WebEx player. Open a WRF file with the player or check Windows File Explorer > Default Apps > Choose default apps by file type for .wrf extension. Confirm the WebEx WRF Player handles these files.Affected if WRF file handling is active and the vulnerable player processes WRF files
-
Inspect recent WRF file accessReview system logs, antivirus logs, or WebEx player logs for recent .wrf file openings. Check browser download history or recent documents for any .wrf files that may have been opened. On Windows, check Event Viewer under Windows Logs > Application for WebEx-related events.Affected if Users have opened WRF files on the affected system, which would trigger the vulnerable code path
A system is affected if Cisco WebEx WRF Player version t31.20 or t31.20.2 is installed and WRF file handling is active, allowing malicious WRF files to trigger the out-of-bounds read vulnerability.
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 the Cisco patch or update to the WRF Player; ensure WebEx Business Suite and Meetings sites are running current versions.
Fix this in Webex Meetings Online
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0288 — 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-0288 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