CVE-2013-1115
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 · uneditedBuffer overflow in Cisco WebEx Advanced Recording Format (ARF) player T27 LD before SP32 EP16, T27 L10N before SP32_ORION111, and T28 before T28.8 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted ARF file, aka Bug IDs CSCue74118, CSCub28371, CSCud23401, and CSCud31109.
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 confidenceBuffer overflow vulnerability in Cisco WebEx Advanced Recording Format (ARF) player allows remote attackers to execute arbitrary code or cause memory corruption via specially crafted ARF files. The vulnerability affects multiple versions of the T27 and T28 player software prior to specified patch levels.
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= 27.11.26= 27.21.10= 27.25.10= 27.32.1= 28.0.0CVSS 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 if Cisco WebEx ARF player is installedCheck for WebEx player installation in common locations: Windows typically at C:\Program Files\WebEx\WebEx AT\ or C:\Program Files (x86)\WebEx\WebEx AT\, or check Add/Remove Programs for WebEx entriesAffected if The WebEx ARF player component is present on the system
-
Determine the installed WebEx player versionRight-click the WebEx player executable (typically player.exe or webexat.exe) in the installation folder, select Properties, then view the Details tab for version information. Alternatively, check the Windows registry under HKLM\SOFTWARE\WebEx\WebEx AT or HKCU\Software\WebEx\WebEx AT for version keysAffected if Unable to determine version or version information is missing
-
Compare installed version against affected versionsMatch the identified version against the affected list: 27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0. If the version matches exactly one of these, it is affected. If the version is lower than any listed version or within the T27/T28 family but unlisted, treat as potentially affectedAffected if The installed version exactly matches 27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0, or falls within the T27/T28 family below the fixed patch levels (SP32 EP16 for T27 LD, SP32_ORION111 for T27 L10N, or T28.8 for T28)
-
Verify ARF file handling capability is presentCheck if the system has .arf file association configured for the WebEx player, or verify that the WebEx recording editor component (wraceditor.exe or similar) is installed, as this component processes ARF filesAffected if ARF file associations or recording editor components are configured on the system
A user is affected if the Cisco WebEx ARF player is installed with a version matching 27.11.26, 27.21.10, 27.25.10, 27.32.1, or 28.0.0 (or any T27/T28 version prior to the fixed patch levels) and the ARF file handling capability is present on the system.
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 · scopedUpdate Cisco WebEx ARF player to version SP32 EP16 or later for T27 LD, SP32_ORION111 or later for T27 L10N, and T28.8 or later for T28. Users should not open untrusted ARF files from unknown sources.
Upgrade to T27 LD SP32 EP16 / T27 L10N SP32_ORION111 / T28.8 or later depending on your release train
- 1. Identify the exact version of Cisco WebEx Advanced Recording Format (ARF) Player currently installed by checking About or Help > About in the player
- 2. Determine which release train the current version belongs to: T27 LD, T27 L10N, or T28
- 3. For T27 LD releases: upgrade to SP32 EP16 or later
- 4. For T27 L10N releases: upgrade to SP32_ORION111 or later
- 5. For T28 releases: upgrade to T28.8 or later
- 6. Obtain the updated player from Cisco's official download channels or through your organization's WebEx distribution
- 7. Verify the installation by checking the version number after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1115 — 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-2013-1115 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