dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2013-1118

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
Stack-based buffer overflow 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 via a crafted WRF file, aka Bug ID CSCuc27645.

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

Stack-based buffer overflow in Cisco WebEx Recording Format (WRF) player allows remote attackers to execute arbitrary code via a crafted WRF file. Affected versions include T27 LD before SP32 EP16, T27 L10N before SP32_ORION111, and T28 before T28.8.

MitigationUpdate the WebEx WRF player to the patched versions (SP32 EP16 or later for T27 LD, SP32_ORION111 or later for T27 L10N, and T28.8 or later for T28) to remediate this vulnerability.

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. Confirm WebEx WRF Player is installed
    Check for the presence of Cisco WebEx Recording Format Player on the system. On Windows, look for 'WebEx WRF Player' or 'WebEx Recording Format Player' in Programs and Features, or check for the executable (typically in C:\Program Files\WebEx\ or similar). On Mac, check /Applications for WebEx components.
    Affected if The WRF player is installed on the system.
  2. Identify the installed WRF player version
    Right-click the WRF player executable (often named wrfplayer.exe or similar), select Properties, then navigate to the Details tab to view the File Version. Alternatively, open a WRF file with the player and check Help > About WebEx, or use the command: wmic product where "name like '%WebEx%'" get version
    Affected if A version number is returned that can be compared against the affected ranges.
  3. Compare version against affected T27 LD range
    If the version begins with 27.x (such as 27.11.26, 27.21.10, 27.25.10, 27.32.1, 27.32.10), check if it is before SP32 EP16. These are T27 LD versions.
    Affected if The version is 27.x and is earlier than SP32 EP16.
  4. Compare version against affected T27 L10N range
    If the version appears to be a localized T27 version (T27 L10N), check if it is before SP32_ORION111.
    Affected if The version is T27 L10N and is earlier than SP32_ORION111.
  5. Compare version against affected T28 range
    If the version begins with 28.x (such as 28.0.0 or 28.4), check if it is earlier than T28.8.
    Affected if The version is 28.x and is earlier than T28.8.

The system is affected if the Cisco WebEx Recording Format Player is installed and its version falls within 27.x before SP32 EP16, 27.x before SP32_ORION111 (L10N), or 28.x 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 the WebEx WRF player to the patched versions (SP32 EP16 or later for T27 LD, SP32_ORION111 or later for T27 L10N, and T28.8 or later for T28) to remediate this vulnerability.

Recommended fix High confidence

SP32 EP16 (T27 LD), SP32_ORION111 (T27 L10N), or T28.8 (T28) - or any subsequent release

  1. 1. Identify the exact Cisco WebEx Recording Format (WRF) Player version currently installed
  2. 2. Determine the product line (T27 LD, T27 L10N, or T28) from the installed version number
  3. 3. For T27 LD versions before SP32 EP16: upgrade to SP32 EP16 or later
  4. 4. For T27 L10N versions before SP32_ORION111: upgrade to SP32_ORION111 or later
  5. 5. For T28 versions before T28.8: upgrade to T28.8 or later
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Test that WRF files open correctly in the updated player
Caveat Minor: Review release notes for any changes to recording format compatibility or deprecated features

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

Fix this in Webex Recording Format Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1118 — 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-1118 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