# CVE-2015-8773: Memory corruption in n/a

> Attackers can cause a system crash in McAfee Total Protection via a stack-based buffer overflow in the File Lock driver.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7p59-xqgx-w7p8

## What is CVE-2015-8773?

CVE-2015-8773 is a high-severity memory corruption vulnerability in n/a, published on 29 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in McPvDrv.sys 4.6.111.0 in McAfee File Lock 5.x in McAfee Total Protection allows attackers to cause a denial of service (system crash) via a long vault GUID in an ioctl call.

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

## Which versions are affected by CVE-2015-8773?

It affects 1 product.


Products: Mcafee File Lock.

## How do I fix CVE-2015-8773?

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

## Is CVE-2015-8773 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8772](https://insights.sbomify.com/CVE-2015-8772/): Integer overflow in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8773 and fix it if it is affected.

What it is: CVE-2015-8773 is a high-severity memory corruption vulnerability in n/a, published on 29 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8773 in the wild and no public exploit code.

Affected product: n/a. 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-2015-8773/ (Markdown: https://insights.sbomify.com/CVE-2015-8773/index.md)
```

## Sources

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

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