Webex Recording Format PlayerApplication · Cisco
CVE-2012-3055
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 · uneditedStack-based buffer overflow in the Cisco WebEx Recording Format (WRF) player T27 L through SP11 EP26, T27 LB through SP21 EP10, T27 LC before SP25 EP11, T27 LD before SP32 CP2, and T28 L10N before SP1 allows remote attackers to execute arbitrary code via a crafted DHT chunk in a JPEG image within a WRF file, aka Bug ID CSCtz72953.
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 confidenceStack-based buffer overflow in Cisco WebEx WRF player when parsing specially crafted JPEG images containing malformed DHT (Define Huffman Table) chunks within WRF files. Successful exploitation allows remote attackers to execute arbitrary code via a malicious WRF file.
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
>= 27.11.0, <= 27.11.26>= 27.21.0, <= 27.21.10>= 27.25.0, < 27.25.11>= 27.32.0, < 27.32.2>= 28.0.0, < 28.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco WebEx WRF Player installationSearch for WebEx player executables (such as 'atgwebexplayer.exe', 'webexplayer.exe', or similar) in Program Files directories or the application's installation folder. The player is typically installed under a Cisco or WebEx folder.Affected if The player executable exists on the system
-
Retrieve the installed player versionRight-click the identified WebEx WRF player executable, select Properties, and view the Version tab. Alternatively, right-click the executable, select Properties, and check the Details section for Product Version or File Version.Affected if The version number cannot be determined or is not visible
-
Compare version against affected rangesIf the version is identified, compare it to these vulnerable ranges: 27.11.0 through 27.11.26, 27.21.0 through 27.21.10, 27.25.0 through 27.25.10, 27.32.0 through 27.32.1, or 28.0.0. Match the major.minor.build format exactly.Affected if The installed version falls within any of these ranges: >= 27.11.0 and <= 27.11.26, OR >= 27.21.0 and <= 27.21.10, OR >= 27.25.0 and < 27.25.11, OR >= 27.32.0 and < 27.32.2, OR >= 28.0.0 and < 28.0.1
-
Verify WRF file parsing is availableConfirm that the WebEx player is configured to handle .wrf file associations or is used within WebEx client tools for recording playback. Check if the player handles embedded JPEG images within WRF files.Affected if The player processes WRF files containing embedded JPEG content and the version is in the affected range
A user is affected if the Cisco WebEx Recording Format Player is installed with a version number matching any of the specified vulnerable ranges (27.11.0-27.11.26, 27.21.0-27.21.10, 27.25.0-27.25.10, 27.32.0-27.32.1, or 28.0.0) and the player is used to open untrusted WRF files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped27.25.1127.32.228.0.1
Organizations should update to the patched versions of Cisco WebEx player (T27 LC SP25 EP11+, T27 LD SP32 CP2+, T28 L10N SP1+, or later) and restrict users from opening untrusted WRF files from unverified sources.
Latest available WRF Player release (minimum: T27 L SP11 EP27+, T27 LB SP21 EP11+, T27 LC SP25 EP11+, T27 LD SP32 CP2+, or T28 L10N SP1+)
- 1. Identify the currently installed WebEx Recording Format (WRF) Player version from the Help > About menu
- 2. Determine which release branch (T27 L, T27 LB, T27 LC, T27 LD, or T28 L10N) your current version belongs to
- 3. For T27 L branch: upgrade to SP11 EP27 or later
- 4. For T27 LB branch: upgrade to SP21 EP11 or later
- 5. For T27 LC branch: upgrade to SP25 EP11 or later
- 6. For T27 LD branch: upgrade to SP32 CP2 or later
- 7. For T28 L10N branch: upgrade to SP1 or later
- 8. Alternatively, download the latest WRF Player version from the official Cisco WebEx download page to ensure all security patches are included
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
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 locallyCheck whether your project pulls in CVE-2012-3055 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3055 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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