dbcve.org
Webex Advanced Recording Format PlayerApplication · Cisco

CVE-2014-2136

HIGH · 9.3 CVSS v2.0 Published 2014-05-08
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 Advanced Recording Format (ARF) player T27 LD before SP32 EP16, T28 before T28.12, and T29 before T29.2 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted .arf file, aka Bug IDs CSCui72223, CSCul01163, and CSCul01166.

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 Advanced Recording Format (ARF) player allows remote code execution or denial of service via a maliciously crafted .arf file. The vulnerability affects T27 LD before SP32 EP16, T28 before T28.12, and T29 before T29.2.

MitigationUpdate Cisco ARF player to patched versions: T27 LD to SP32 EP16 or later, T28 to T28.12 or later, and T29 to T29.2 or later. Until patched, avoid opening untrusted .arf 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 Advanced Recording Format PlayerApplication
Affected:= t27ld= t28= t29
Webex Recording Format PlayerApplication
Affected:= t27ld= t28= t29

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 Cisco Webex ARF player is installed
    Check for Cisco Webex Advanced Recording Format Player or Cisco Webex Recording Format Player on the system. Look for the player executable or check Windows Add/Remove Programs for Webex components.
    Affected if The player software is present on the system
  2. Identify the installed version family
    Open the ARF player and check About/Version information, or locate the player executable in the installation directory and view its version properties.
    Affected if The version family is t27ld, t28, or t29
  3. Compare version against fixed releases
    For T27 LD: verify if version is earlier than SP32 EP16. For T28: verify if version is earlier than T28.12. For T29: verify if version is earlier than T29.2.
    Affected if The installed version falls before the patched release for its family (T27 LD < SP32 EP16, T28 < T28.12, or T29 < T29.2)
  4. Assess exposure to malicious .arf files
    Determine if the user routinely opens .arf files from external or untrusted sources, or if the player is configured to automatically handle .arf file associations.
    Affected if The player handles .arf files from potentially untrusted sources

A user is affected if Cisco Webex ARF/ARF player is installed with version t27ld before SP32 EP16, t28 before T28.12, or t29 before T29.2, and the player is used to open .arf files.

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 ARF player to patched versions: T27 LD to SP32 EP16 or later, T28 to T28.12 or later, and T29 to T29.2 or later. Until patched, avoid opening untrusted .arf files.

Recommended fix High confidence

T27 LD to SP32 EP16, T28 to T28.12, T29 to T29.2

  1. Identify the installed Cisco Webex ARF player version (t27ld, t28, or t29)
  2. Navigate to the Cisco Webex download page or use the built-in update mechanism in the Webex player
  3. For T27 LD: Upgrade to version SP32 EP16 or later
  4. For T28: Upgrade to version T28.12 or later
  5. For T29: Upgrade to version T29.2 or later
  6. Restart the Webex player after applying the update
  7. Verify the installed version matches or exceeds the fixed release

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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