dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2013-1117

HIGH · 9.3 CVSS v2.0 Published 2013-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer overflow in the exception handler in Cisco WebEx Recording Format (WRF) player T27 LD before SP32 EP16, T27 L10N before SP32_ORION111, and T28 before T28.8 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted WRF file, aka Bug ID CSCuc27639.

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 confidence

Buffer overflow vulnerability in the exception handler of Cisco WebEx Recording Format (WRF) player affects T27 LD versions before SP32 EP16, T27 L10N before SP32_ORION111, and T28 before T28.8. Attackers can exploit by tricking users into opening crafted WRF files, leading to arbitrary code execution or memory corruption causing denial of service.

MitigationUpdate Cisco WebEx WRF player to patched versions (T27 LD SP32 EP16 or later, T27 L10N SP32_ORION111 or later, or T28.8 or later) and educate users to avoid opening untrusted WRF files.

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 Recording Format PlayerApplication
Affected:= 27.11.26= 27.21.10= 27.25.10= 27.32.1= 27.32.10= 28.0.0= 28.4

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WebEx WRF Player is installed
    Check for the presence of Cisco WebEx WRF player on the system. Look for executable files such as 'gdrwc.dll', 'GRFWn.dll', or the WebEx player application in Program Files. On Windows, check Add/Remove Programs or the installed programs list for 'Cisco WebEx Recording Format Player' or similar naming.
    Affected if The Cisco WebEx WRF Player is found installed on the system.
  2. Identify the installed WRF player version
    Locate the version information for the installed WRF player. Check the file properties of the main executable or DLL (commonly found in the WebEx installation directory), or use the Windows registry under HKLM\Software\Cisco Systems or HKCU\Software\Cisco Systems if available. The version typically appears in the format like 27.x.x.x or 28.x.x.
    Affected if A version number is found that matches or falls within the affected ranges: 27.11.26, 27.21.10, 27.25.10, 27.32.1, 27.32.10, 28.0.0, 28.4, or any T27 LD version before SP32 EP16, T27 L10N before SP32_ORION111, or T28 before T28.8.
  3. Confirm the WRF file handler is active
    Check if .wrf file associations are configured to open with the WebEx WRF player. On Windows, verify this through Control Panel > Default Programs > File Associations, or check the registry under HKCR\.wrf. Also verify the player can be invoked by attempting to open or listing associated applications for .wrf files.
    Affected if The .wrf file extension is associated with the installed WebEx player, meaning the player would process WRF files if opened by a user.
  4. Check for any installed service packs or updates
    If a version in the 27.x or 28.x range is found, determine if any service packs are installed. Look in Add/Remove Programs for entries like 'SP32 EP16', 'SP32_ORION111', or 'T28.8', or check the program's About or Help > About section if accessible. The version info may include the SP level in the detailed properties.
    Affected if No service pack (SP32 EP16, SP32_ORION111, or T28.8) is installed, confirming the player remains at a vulnerable version level.

A user is affected if the Cisco WebEx WRF Player is installed with any of the specific vulnerable versions (27.11.26, 27.21.10, 27.25.10, 27.32.1, 27.32.10, 28.0.0, 28.4) or falls within the version ranges (T27 LD before SP32 EP16, T27 L10N before SP32_ORION111, or T28 before T28.8).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Cisco WebEx WRF player to patched versions (T27 LD SP32 EP16 or later, T27 L10N SP32_ORION111 or later, or T28.8 or later) and educate users to avoid opening untrusted WRF files.

Recommended fix High confidence

T27 LD: SP32 EP16 or later; T27 L10N: SP32_ORION111 or later; T28: T28.8 or later

  1. Identify the exact version and build of WebEx Recording Format Player installed (e.g., T27 LD, T27 L10N, or T28 branch)
  2. For T27 LD versions before SP32 EP16: upgrade to SP32 EP16 or later
  3. For T27 L10N versions before SP32_ORION111: upgrade to SP32_ORION111 or later
  4. For T28 versions before T28.8: upgrade to T28.8 or later
  5. Verify the upgrade was successful by checking the updated version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webex Recording Format Player Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1117 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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