dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2012-1335

HIGH · 9.3 CVSS v2.0 Published 2012-04-05
Fix available
A fix is available. Upgrade to 27.25.10 / 27.32.1 or later.
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 Cisco WebEx Recording Format (WRF) player T27 L through SP11 EP26, T27 LB through SP21 EP10, T27 LC before SP25 EP10, and T27 LD before SP32 CP1 allows remote attackers to execute arbitrary code via a crafted WRF file, a different vulnerability than CVE-2012-1336 and CVE-2012-1337.

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 in Cisco WebEx Recording Format (WRF) player allows remote attackers to execute arbitrary code via a crafted WRF file. The vulnerability affects multiple branches (L, LB, LC, LD) of T27 player at specific SP/EP versions. This is a client-side code execution vulnerability with high severity (CVSS 9.3).

MitigationApply vendor patches: Update T27 LC to SP25 EP10 or later, T27 LD to SP32 CP1 or later, and apply corresponding patches for L and LB branches. Implement network controls to block untrusted WRF files until patching is complete.

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.0, <= 27.11.26>= 27.21.0, <= 27.21.10>= 27.25.0, < 27.25.10>= 27.32.0, < 27.32.1

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 the WebEx WRF Player version
    Open the WebEx Recording Format Player, access the About or Help menu, and locate the version information. Alternatively, check the installed program's version property in the Windows Add/Remove Programs or macOS Applications folder.
    Affected if The displayed version falls within any of these ranges: 27.11.0 to 27.11.26, 27.21.0 to 27.21.10, 27.25.0 to 27.25.9, or 27.32.0 to 27.32.0
  2. Determine the T27 branch and service pack version
    Check the full version string which typically includes branch identifiers (L, LB, LC, LD) along with SP (Service Pack) and EP (Extension Pack) numbers. This information is usually visible in the player About dialog or the installer properties.
    Affected if The branch is L, LB, LC, or LD with an SP/EP version below the patched levels for that branch (for LC: below SP25 EP10; for LD: below SP32 CP1)
  3. Verify if WRF file association is active
    Check if .wrf file type is registered to open with the WebEx WRF Player. On Windows, inspect file associations in Control Panel > Default Programs. On macOS, check Get Info for a .wrf file.
    Affected if WRF files are associated with the vulnerable player version detected in step 1 or 2
  4. Inspect recent WRF file processing activity
    Review the system for any recently opened or processed .wrf files. Check browser download folders, email attachments, or shared network locations where WRF files may have been opened.
    Affected if The system has processed .wrf files with the vulnerable player installed, indicating potential exploitation vector

A system is affected if the WebEx WRF Player version matches any of the affected version ranges (27.11.x, 27.21.x, 27.25.x before 27.25.10, or 27.32.x before 27.32.1) and the player processes WRF files from untrusted sources.

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
Upgrade available Upgrade to 27.25.10 / 27.32.1 or later
Fixed in 27.25.1027.32.1
Interim mitigation

Apply vendor patches: Update T27 LC to SP25 EP10 or later, T27 LD to SP32 CP1 or later, and apply corresponding patches for L and LB branches. Implement network controls to block untrusted WRF files until patching is complete.

Recommended fix High confidence

Latest WRF Player version (27.32.1+ for T27 LD, or the most recent available for your branch)

  1. 1. Identify the current installed version of Cisco WebEx Recording Format (WRF) Player by opening the player and checking About or checking Add/Remove Programs.
  2. 2. Determine which version branch you are on (T27 L, T27 LB, T27 LC, or T27 LD) based on your version number.
  3. 3. For T27 L branch (versions 27.11.0-27.11.26): Upgrade to version 27.11.27 or later.
  4. 4. For T27 LB branch (versions 27.21.0-27.21.10): Upgrade to version 27.21.11 or later.
  5. 5. For T27 LC branch (versions 27.25.0-27.25.9): Upgrade to SP25 EP10 or later version.
  6. 6. For T27 LD branch (versions 27.32.0): Upgrade to SP32 CP1 or later version (27.32.1 or higher).
  7. 7. Download the fixed version from Cisco's official download site or through your Cisco support contract at tools.cisco.com.
  8. 8. Uninstall the current WRF Player version through Windows Control Panel > Programs and Features.
Caveat Standard upgrade - minimal risk; ensure you have backups of critical WRF recording files before upgrading

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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