# CVE-2018-0103: Memory corruption in Cisco WebEx Network Recording Player

> A buffer overflow in Cisco WebEx Network Recording Player allows attackers to execute arbitrary code via malicious ARF files.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 4 Jan 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-xjqv-vp4w-g4g9

## What is CVE-2018-0103?

CVE-2018-0103 is a high-severity memory corruption vulnerability in Cisco Webex Meetings, published on 4 Jan 2018. 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

A Buffer Overflow vulnerability in Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) files could allow a local attacker to execute arbitrary code on the system of a user. The attacker could exploit this vulnerability by sending the user a link or email attachment with a malicious ARF file and persuading the user to follow the link or launch the file. Successful exploitation could allow the attacker to execute arbitrary code on the user's system. This vulnerability affects Cisco WebEx Business Suite meeting sites, Cisco WebEx Meetings sites, Cisco WebEx Meetings Server, and Cisco WebEx ARF players. Cisco Bug IDs: CSCvg78835, CSCvg78837, CSCvg78839.

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

## Which versions are affected by CVE-2018-0103?

It affects 4 products.


Products: Cisco Webex Business Suite, Cisco Webex Meetings, Cisco Webex Meetings Server, Cisco Webex Network Recording Player.

## How do I fix CVE-2018-0103?

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

## Is CVE-2018-0103 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2018-0104](https://insights.sbomify.com/CVE-2018-0104/): Code injection in Cisco WebEx Advanced Recording Format Player (critical 9.6)
- [CVE-2019-15284](https://insights.sbomify.com/CVE-2019-15284/): Cisco Webex Network Recording Player and Cisco Webex Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-15286](https://insights.sbomify.com/CVE-2019-15286/): Cisco Webex Network Recording Player and Cisco Webex Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-1924](https://insights.sbomify.com/CVE-2019-1924/): Cisco Webex Network Recording Player and Cisco Webex Player Arbitrary Code Execution Vulnerabilities (high 7.8)
- [CVE-2019-1925](https://insights.sbomify.com/CVE-2019-1925/): Cisco Webex Network Recording Player and Cisco Webex Player Arbitrary Code Execution Vulnerabilities (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0103 and fix it if it is affected.

What it is: CVE-2018-0103 is a high-severity memory corruption vulnerability in Cisco Webex Meetings, published on 4 Jan 2018. 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-2018-0103 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-2018-0103/ (Markdown: https://insights.sbomify.com/CVE-2018-0103/index.md)
```

## Sources

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

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