dbcve.org
Webex Recording Format PlayerApplication · Cisco

CVE-2011-3319

HIGH · 9.3 CVSS v2.0 Published 2011-10-27
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 WRF parsing functionality in the Cisco WebEx Recording Format (WRF) player T26 before SP49 EP40 and T27 before SP28 allows remote attackers to execute arbitrary code via a crafted WRF file.

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 the WRF (WebEx Recording Format) file parser in Cisco WebEx Player versions T26 before SP49 EP40 and T27 before SP28. A remote attacker can achieve arbitrary code execution by tricking a user into opening a specially crafted malicious WRF file.

MitigationApply vendor patches by updating to WebEx Player T26 SP49 EP40 or later, or T27 SP28 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:= 26= 27= 27.10= 27.12= 27.13

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 Player installation
    Search for WebEx Player executable (wrqview.exe or WebExPlayer.exe) in common installation directories: C:\Program Files\Cisco Systems\WebEx\WebEx Recording Format Player\ or C:\Program Files\WebEx\
    Affected if WebEx Player is installed on the system
  2. Identify installed WebEx Player version
    Right-click the WebEx Player executable, select Properties, and check the Version tab. Alternatively, run the player and look for version information in Help > About, or use command: wrqview.exe /version
    Affected if Version displays as T26 with SP less than 49 EP40, or T27 with SP less than 28, or versions 27.10.x, 27.12.x, 27.13.x
  3. Confirm version family (T26 or T27)
    Examine the version string: if it starts with "T26" it belongs to the T26 family; if it starts with "T27" it belongs to the T27 family. Also check for build numbers in the format like "26.x.x.x" or "27.x.x.x"
    Affected if Version family is T26 or T27 with patch level below the fixed versions
  4. Compare against vulnerability thresholds
    For T26 family: verify if SP (Service Pack) is below 49, or if SP49 but EP (Emergency Patch) is below 40. For T27 family: verify if SP is below 28. Version format typically appears as T26 SPxx EPyy or T27 SPxx
    Affected if T26 version is earlier than SP49 EP40, or T27 version is earlier than SP28

User is affected if Cisco WebEx Player T26 or T27 is installed with a version earlier than T26 SP49 EP40 or T27 SP28, respectively, 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches by updating to WebEx Player T26 SP49 EP40 or later, or T27 SP28 or later. Until patched, avoid opening WRF files from untrusted sources.

Recommended fix High confidence

T26 SP49 EP40 or later; T27 SP28 or later

  1. Navigate to the Cisco WebEx downloads page or contact Cisco support for the WebEx Recording Format (WRF) player
  2. For T26 product line: Download and install Service Pack 49 EP40 or later
  3. For T27 product line: Download and install Service Pack 28 or later
  4. Verify the installed version matches the security patch level (SP49 EP40 for T26, SP28 for T27)
Caveat None expected - this is a security patch update

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

Fix this in Webex Recording Format Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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