# CVE-2017-6669: Memory corruption in Cisco WebEx Network Recording Player

> Buffer overflows in Cisco WebEx Network Recording Player allow arbitrary code execution or crashes when users open malicious ARF files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rvqf-c4mj-p3xw

## What is CVE-2017-6669?

CVE-2017-6669 is a high-severity memory corruption vulnerability in Cisco WebEx Network Recording Player, published on 26 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple buffer overflow vulnerabilities exist in the Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) files. An attacker could exploit these vulnerabilities by providing a user with a malicious ARF file via email or URL and convincing the user to launch the file. Exploitation of these vulnerabilities could cause an affected player to crash and, in some cases, could allow arbitrary code execution on the system of a targeted user. The Cisco WebEx Network Recording Player is an application that is used to play back WebEx meeting recordings that have been recorded on the computer of an online meeting attendee. The player can be automatically installed when the user accesses a recording file that is hosted on a WebEx server. The following client builds are affected by this vulnerability: Cisco WebEx Business Suite (WBS29) client builds prior to T29.13.130, Cisco WebEx Business Suite (WBS30) client builds prior to T30.17, Cisco WebEx Business Suite (WBS31) client builds prior to T31.10. Cisco Bug IDs: CSCvc47758 CSCvc51227 CSCvc51242.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-6669?

It affects 1 product.


Products: Cisco Webex Advanced Recording Format Player.

## How do I fix CVE-2017-6669?

No fix has been published for CVE-2017-6669 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6669 being exploited?

There is no known exploitation of CVE-2017-6669 in the wild and no public exploit code.

## Other vulnerabilities in Cisco WebEx Network Recording Player

- [CVE-2014-2133](https://insights.sbomify.com/CVE-2014-2133/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-2134](https://insights.sbomify.com/CVE-2014-2134/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-2135](https://insights.sbomify.com/CVE-2014-2135/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-2136](https://insights.sbomify.com/CVE-2014-2136/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-1115](https://insights.sbomify.com/CVE-2013-1115/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6669 and fix it if it is affected.

What it is: CVE-2017-6669 is a high-severity memory corruption vulnerability in Cisco WebEx Network Recording Player, published on 26 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6669 in the wild and no public exploit code.

Affected product: Cisco WebEx Network Recording Player. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6669/ (Markdown: https://insights.sbomify.com/CVE-2017-6669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6669
- OSV: https://osv.dev/vulnerability/CVE-2017-6669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6669/
Summaries are generated and may contain mistakes; the official description above is the record.