dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2012-1336

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-1335 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 vulnerability in Cisco WebEx Recording Format (WRF) player allows remote code execution via specially crafted WRF files. Multiple version branches (T27 L through SP11 EP26, T27 LB through SP21 EP10, T27 LC before SP25 EP10, and T27 LD before SP32 CP1) are affected. The vulnerability requires user interaction to open a malicious file but achieves code execution with high impact.

MitigationApply vendor patches or update WebEx WRF player to the latest version. 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.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. Locate WebEx WRF Player installation
    Search for WebEx player executables (typically named ARFPlayer.exe, GSRHelper.exe, or similar WebEx player components) in Program Files directories or check Windows registry under HKLM\SOFTWARE\Cisco Systems for WebEx recording editor or player entries
    Affected if WebEx WRF player is found but version cannot be determined or falls within affected ranges
  2. Extract player version information
    Right-click the player executable, select Properties, and check the Details tab for File Version; alternatively, run 'wmic product get name,version' or use PowerShell 'Get-ItemProperty' on the executable to retrieve version metadata
    Affected if Version number matches 27.11.0 through 27.11.26, 27.21.0 through 27.21.10, 27.25.0 through 27.25.9, or 27.32.0
  3. Verify WRF file association is active
    Check Windows registry under HKCR\.wrf or HKLM\SOFTWARE\Classes\.wrf to confirm WRF files are associated with the WebEx player; also check HKCR\WRFFile\shell\open\command for the player path
    Affected if WRF file association points to a WebEx player executable that is the vulnerable version found in step 2
  4. Confirm player component is present
    Look for WebEx recording-related DLLs or executables in the installation directory (commonly in C:\Program Files\WebEx\ or similar); verify the specific WRF playback component exists
    Affected if The WRF player component exists and its version matches the vulnerable ranges

If the installed WebEx WRF player version falls within 27.11.0-27.11.26, 27.21.0-27.21.10, 27.25.0-27.25.9, or 27.32.0, and WRF file handling is enabled, the environment is affected by this vulnerability.

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 or update WebEx WRF player to the latest version. Until patched, avoid opening WRF files from untrusted sources.

Recommended fix High confidence

T27 LC to SP25 EP10 or later; T27 LD to SP32 CP1 or later; T27 L/LB to latest stable release beyond vulnerable ranges

  1. Identify the T27 release line (L, LB, LC, or LD) currently installed by checking the WebEx player version information
  2. For T27 LC: upgrade to SP25 EP10 or later version
  3. For T27 LD: upgrade to SP32 CP1 or later version
  4. For T27 L (SP11 and earlier): upgrade to a release beyond SP11 EP26
  5. For T27 LB (SP21 and earlier): upgrade to a release beyond SP21 EP10
  6. After upgrading, verify the new version is no longer within the vulnerable ranges
  7. Test that WRF files still function correctly after the upgrade

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

Fix this in Webex Recording Format Player Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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