# CVE-2018-0379: Memory corruption in Cisco Webex Network Recording Players unknown

> Attackers can execute arbitrary code by tricking users into opening malicious ARF or WRF files in Cisco Webex Network Recording Players.

- **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:** 18 Jul 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-w494-3p63-x3xx

## What is CVE-2018-0379?

CVE-2018-0379 is a high-severity memory corruption vulnerability in Cisco Webex Meetings Online, published on 18 Jul 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

Multiple vulnerabilities exist in the Cisco Webex Network Recording Player for Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker could exploit these vulnerabilities by providing a user with a malicious .arf or .wrf file via email or URL and convincing the user to launch the file in the Webex recording players. Exploitation of these vulnerabilities could allow arbitrary code execution on the system of a targeted user. These vulnerabilities affect ARF and WRF recording players available from Cisco Webex Meetings Suite sites, Cisco Webex Meetings Online sites, and Cisco Webex Meetings Server. Cisco Bug IDs: CSCvi02621, CSCvi02965, CSCvi63329, CSCvi63333, CSCvi63335, CSCvi63374, CSCvi63376, CSCvi63377, CSCvi63391, CSCvi63392, CSCvi63396, CSCvi63495, CSCvi63497, CSCvi63498, CSCvi82684, CSCvi82700, CSCvi82705, CSCvi82725, CSCvi82737, CSCvi82742, CSCvi82760, CSCvi82771, CSCvj51284, CSCvj51294.

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

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

It affects 3 products.


Products: Cisco Webex Business Suite, Cisco Webex Meeting Server, Cisco Webex Meetings Online.

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

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

## Is CVE-2018-0379 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings Online

- [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-0379 and fix it if it is affected.

What it is: CVE-2018-0379 is a high-severity memory corruption vulnerability in Cisco Webex Meetings Online, published on 18 Jul 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-0379 in the wild and no public exploit code.

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

## Sources

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

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