dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2013-1119

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 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 DHT index value in JPEG data within a WRF file, aka Bug ID CSCuc24503.

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 Cisco WebEx Recording Format (WRF) player allows remote code execution via crafted WRF files containing malicious JPEG data with a manipulated DHT (Define Huffman Table) index value. The overflow leads to memory corruption, enabling arbitrary code execution or denial of service.

MitigationApply vendor patches: update T27 LD to SP32 EP16, T27 L10N to SP32_ORION111, or T28 to T28.8 or later. Until patched, avoid opening WRF files from untrusted sources.

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. Identify if WebEx WRF Player is installed
    Check installed programs list, or search for WebEx recording player executables in typical installation directories such as Program Files. Common executable names include wrfplayer.exe or similar WebEx recording related files.
    Affected if The Cisco WebEx Recording Format Player is present on the system
  2. Retrieve the installed player version
    Right-click the player executable and view Properties > Details to read the File Version, or use system inventory tools to query the installed version of the WebEx WRF Player software.
    Affected if A version number is returned that matches one of the vulnerable releases
  3. Compare version against affected releases
    Match the retrieved version against these vulnerable versions: 27.11.26, 27.21.10, 27.25.10, 27.32.1, 27.32.10, 28.0.0, or 28.4
    Affected if The installed version exactly equals any of the listed version numbers

A user is affected if the Cisco WebEx Recording Format Player is installed and its version matches one of the specifically vulnerable releases: 27.11.26, 27.21.10, 27.25.10, 27.32.1, 27.32.10, 28.0.0, or 28.4.

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

Apply vendor patches: update T27 LD to SP32 EP16, T27 L10N to SP32_ORION111, or T28 to T28.8 or later. Until patched, avoid opening WRF files from untrusted sources.

Recommended fix High confidence

Cisco WebEx Recording Format Player T27 LD SP32 EP16 / T27 L10N SP32_ORION111 / T28.8 or later

  1. 1. Identify the current version of Cisco WebEx Recording Format Player installed by accessing the player's About or Help menu
  2. 2. Determine the product line (T27 LD, T27 L10N, or T28) from the 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. Obtain the updates from Cisco's official download center or through your Cisco support contract
  7. 7. Verify the installation 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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