dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2012-1337

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-1336.

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 attackers to execute arbitrary code via specially crafted WRF files. The vulnerability affects multiple version branches (T27 L through SP11 EP26, T27 LB through SP21 EP10, T27 LC before SP25 EP10, T27 LD before SP32 CP1) and is distinct from related CVEs-1335 and CVE-1336.

MitigationUpdate Cisco WebEx WRF player to patched versions: T27 LC to SP25 EP10 or later, T27 LD to SP32 CP1 or later, and ensure T27 L and T27 LB branches are at their respective patched releases to prevent code execution via malicious WRF 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 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. Verify WebEx WRF Player installation
    On Windows, open Control Panel > Programs and Features or use 'Get-ItemProperty' in PowerShell for installed programs containing 'WebEx' or 'WRF'. On Mac, check /Applications folder for WebEx-related applications.
    Affected if Cisco WebEx Recording Format Player is not found in the system, the system is not affected.
  2. Locate the installed WRF player version
    In Windows, right-click the WebEx player in Programs and Features, select Properties, and view the Version field. Alternatively, use command: reg query 'HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall' /s /f WebEx or inspect the player executable directly.
    Affected if Unable to determine the version number, manual verification of the player executable may be required.
  3. Compare version against affected ranges
    Match your installed version (format 27.xx.x) against: 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 through 27.32.0. If the version matches any of these ranges, the installation is vulnerable.
    Affected if Installed version falls within any of the four affected ranges listed above.
  4. Confirm WRF file handling capability
    Check if the player is configured to automatically open .wrf files or if users have the ability to open WRF files. This can be verified by checking file association settings or recent file access logs for .wrf extensions.
    Affected if The player is present and capable of processing WRF files, making it exploitable if the version is vulnerable.

A system is affected if Cisco WebEx Recording Format Player is installed with a version number matching any of the four vulnerable ranges (27.11.0-27.11.26, 27.21.0-27.21.10, 27.25.0-27.25.9, or 27.32.0-27.32.0) and the player can open WRF 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.

From vendor data
Upgrade available Upgrade to 27.25.10 / 27.32.1 or later
Fixed in 27.25.1027.32.1
Interim mitigation

Update Cisco WebEx WRF player to patched versions: T27 LC to SP25 EP10 or later, T27 LD to SP32 CP1 or later, and ensure T27 L and T27 LB branches are at their respective patched releases to prevent code execution via malicious WRF files.

Fix this in Webex Recording Format Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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