# CVE-2017-12371: Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players

> Remote attackers can execute arbitrary code or cause denial of service by tricking users into opening malicious WebEx recording files.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9p4p-7m2v-wch8

## What is CVE-2017-12371?

CVE-2017-12371 is a critical memory corruption vulnerability in Cisco Webex Meetings, published on 30 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A "Cisco WebEx Network Recording Player Remote Code Execution Vulnerability" exists in Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) and WebEx Recording Format (WRF) files. A remote attacker could exploit this by providing a user with a malicious ARF or WRF file via email or URL and convincing the user to launch the file. Exploitation of this could cause an affected player to crash and, in some cases, could allow arbitrary code execution on the system of a targeted user. Cisco Bug IDs: CSCvf49650, CSCvg54853, CSCvg54856, CSCvf49697, CSCvg54861, CSCvf49707, CSCvg54867.

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

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

It affects 1 product.


Products: Cisco Webex Meetings.

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

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

## Is CVE-2017-12371 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2017-12368](https://insights.sbomify.com/CVE-2017-12368/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12369](https://insights.sbomify.com/CVE-2017-12369/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12370](https://insights.sbomify.com/CVE-2017-12370/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12372](https://insights.sbomify.com/CVE-2017-12372/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2020-3342](https://insights.sbomify.com/CVE-2020-3342/): Cisco Webex Meetings Desktop App for Mac Update Feature Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12371 is a critical memory corruption vulnerability in Cisco Webex Meetings, published on 30 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12371 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. 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-12371/ (Markdown: https://insights.sbomify.com/CVE-2017-12371/index.md)
```

## Sources

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

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