dbcve.org
Webex Advanced Recording Format PlayerApplication · Cisco

CVE-2013-1116

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 Advanced Recording Format (ARF) 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 (heap memory corruption) via a crafted ARF file, aka Bug IDs CSCue74147 and CSCub28383.

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 · moderate confidence

Heap-based buffer overflow vulnerability in Cisco WebEx Advanced Recording Format (ARF) player allows remote attackers to execute arbitrary code or cause denial of service via specially crafted ARF files. The vulnerability affects multiple versions of T27 and T28 player releases, with patches available in SP32 EP16, SP32_ORION111, and T28.8.

MitigationApply vendor patches by updating to T27 LD SP32 EP16 or later, T27 L10N SP32_ORION111 or later, or T28.8 or later. Until patches are applied, avoid opening untrusted ARF files from unknown 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 Advanced Recording Format PlayerApplication
Affected:= 27.11.26= 27.21.10= 27.25.10= 27.32.1= 28.0.0

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 ARF Player installation
    Check for Cisco WebEx ARF Player on the system by searching for installed programs or looking for the player executable (typically named atplay.exe or similar WebEx recording player files)
    Affected if The player is installed and the system has WebEx ARF software present
  2. Identify installed ARF player version
    Locate the player executable (often in Program Files/Cisco Systems or WebEx folders) and check its file properties, or use system inventory tools to query the installed software version
    Affected if The exact version cannot be determined or the version matches one of the affected releases (27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0)
  3. Compare version against affected releases
    Match your identified installed version against the affected version list: 27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0
    Affected if The installed version equals any of these five specific versions exactly
  4. Confirm ARF file handling capability
    Check if the player is configured to handle .arf files, either as a default application or through browser/plugin integration with WebEx
    Affected if The player can open or automatically process ARF files, enabling the attack surface

A user is affected if Cisco WebEx ARF Player is installed and the exact installed version matches one of the five affected releases: 27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0.

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 by updating to T27 LD SP32 EP16 or later, T27 L10N SP32_ORION111 or later, or T28.8 or later. Until patches are applied, avoid opening untrusted ARF files from unknown sources.

Recommended fix High confidence

Upgrade to Cisco WebEx ARF Player T27 LD SP32 EP16 or later, T27 L10N SP32_ORION111 or later, or T28 T28.8 or later

  1. Identify the exact WebEx ARF Player version installed (T27 LD, T27 L10N, or T28) via the application's Help > About menu
  2. Navigate to the Cisco WebEx download page or Cisco Software Download center
  3. For T27 LD users: Download and install version SP32 EP16 or later
  4. For T27 L10N users: Download and install version SP32_ORION111 or later
  5. For T28 users: Download and install version T28.8 or later
  6. Verify the update was successful by checking the version again

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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