# CVE-2016-8032: Security feature bypass in Anti-Virus Engine (AVE)

> Local attackers can bypass security protections in Intel Anti-Virus Engine by using a crafted input file.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4cjx-2jmj-jg88

## What is CVE-2016-8032?

CVE-2016-8032 is a high-severity vulnerability in Intel Anti-Virus Engine (AVE), published on 31 Mar 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

Software Integrity Attacks vulnerability in Intel Security Anti-Virus Engine (AVE) 5200 through 5800 allows local attackers to bypass local security protection via a crafted input file.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-8032?

It affects 1 product.


Products: Mcafee Anti-Malware Scan Engine.

## How do I fix CVE-2016-8032?

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

## Is CVE-2016-8032 being exploited?

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

## Other vulnerabilities in Intel Anti-Virus Engine (AVE)

- [CVE-2016-8031](https://insights.sbomify.com/CVE-2016-8031/): Security feature bypass in Anti-Virus Engine (AVE) (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8032 and fix it if it is affected.

What it is: CVE-2016-8032 is a high-severity vulnerability in Intel Anti-Virus Engine (AVE), published on 31 Mar 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-2016-8032 in the wild and no public exploit code.

Affected product: Intel Anti-Virus Engine (AVE). 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-2016-8032/ (Markdown: https://insights.sbomify.com/CVE-2016-8032/index.md)
```

## Sources

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

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