dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2012-3938

HIGH · 9.3 CVSS v2.0 Published 2012-10-25
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 the Cisco WebEx Recording Format (WRF) player T27 before LD SP32 EP10 and T28 before T28.4 allows remote attackers to execute arbitrary code via a crafted WRF file, aka Bug ID CSCtz73583.

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

A buffer overflow vulnerability exists in the Cisco WebEx Recording Format (WRF) player versions T27 before LD SP32 EP10 and T28 before T28.4. Attackers can exploit this by crafting malicious WRF files that trigger the overflow, allowing arbitrary code execution on vulnerable systems.

MitigationOrganizations should identify all instances of Cisco WebEx WRF player in their environment and update to the patched versions (T27 LD SP32 EP10 or later, T28 T28.4 or later). 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.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. Locate Cisco WebEx WRF player installation
    Search for WebEx WRF player executables or check standard application installation directories (such as Program Files on Windows). Look for files named 'g2start.exe', 'g2view.exe', or similar WebEx-related executables.
    Affected if Player is not found on the system (not affected)
  2. Determine installed WRF player version
    Right-click the player executable, select Properties, and view the Version tab. Alternatively, run 'g2view.exe -version' or similar command-line version check if available.
    Affected if Unable to determine version (needs further investigation)
  3. Compare version against affected T27 range
    Check if the installed T27 version is one of: 27.11.26, 27.21.10, 27.25.10, 27.32.1, or any version earlier than LD SP32 EP10. These versions are confirmed affected.
    Affected if Version matches one of the listed affected versions or predates LD SP32 EP10
  4. Compare version against affected T28 range
    Check if the installed T28 version is earlier than T28.4 (such as 28.0.0, which is listed as affected).
    Affected if Version is T28 and earlier than T28.4

The environment is affected if Cisco WebEx WRF Player version is T27 (any version before LD SP32 EP10, including 27.11.26, 27.21.10, 27.25.10, 27.32.1) or T28 (any version before T28.4, including 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

Organizations should identify all instances of Cisco WebEx WRF player in their environment and update to the patched versions (T27 LD SP32 EP10 or later, T28 T28.4 or later). Until patched, avoid opening WRF files from untrusted sources.

Recommended fix High confidence

T27: LD SP32 EP10 or later; T28: T28.4 or later

  1. Identify the installed Cisco WebEx Recording Format Player version (T27 or T28 branch)
  2. For T27 versions before LD SP32 EP10: Upgrade to Cisco WebEx Recording Format Player T27 LD SP32 EP10 or later
  3. For T28 versions before T28.4: Upgrade to Cisco WebEx Recording Format Player T28.4 or later
  4. Verify the upgrade was successful by checking the updated version number

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 help mitigating

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-3938 — 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-3938 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