# CVE-2016-4025: Security feature bypass in n/a

> Attackers can bypass the DeepScreen security feature in Avast products via a DeviceIoControl call, allowing malicious code to evade detection.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r6c6-fj9g-rcxw

## What is CVE-2016-4025?

CVE-2016-4025 is a medium-severity vulnerability in n/a, published on 3 Nov 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Avast Internet Security v11.x.x, Pro Antivirus v11.x.x, Premier v11.x.x, Free Antivirus v11.x.x, Business Security v11.x.x, Endpoint Protection v8.x.x, Endpoint Protection Plus v8.x.x, Endpoint Protection Suite v8.x.x, Endpoint Protection Suite Plus v8.x.x, File Server Security v8.x.x, and Email Server Security v8.x.x allow attackers to bypass the DeepScreen feature via a DeviceIoControl call.

Weakness: CWE-254

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

It affects 11 products.


Products: Avast Business Security, Avast Email Server Security, Avast Endpoint Protection, Avast Endpoint Protection Plus, Avast Endpoint Protection Suite, Avast Endpoint Protection Suite Plus, Avast File Server Security, Avast Free Antivirus, Avast Internet Security, Avast Premier, Avast Pro Antivirus.

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

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

## Is CVE-2016-4025 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4025 is a medium-severity vulnerability in n/a, published on 3 Nov 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4025 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-2016-4025/ (Markdown: https://insights.sbomify.com/CVE-2016-4025/index.md)
```

## Sources

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

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