dbcve.org
Business SecurityApplication · Avast

CVE-2016-4025

MEDIUM · 5.5 CVSS v3.0 Published 2016-11-03
Fix available
A fix is available. Upgrade to after 8.0.1609 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Avast security products (v11.x.x and v8.x.x) contain a vulnerability where the DeepScreen security analysis feature can be bypassed through misuse of the Windows DeviceIoControl API call, potentially allowing malicious code to evade detection by this security screening mechanism.

MitigationApply vendor-provided patches for affected Avast products when available. Until then, implement additional endpoint detection and network-based monitoring to compensate for the DeepScreen bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Business SecurityApplication
Affected:= 11.1.2241= 11.1.2245= 11.1.2253= 11.1.2260= 11.1.2261= 11.1.2262
Free AntivirusApplication
Affected:= 11.1.2241= 11.1.2245= 11.1.2253= 11.1.2260= 11.1.2261= 11.1.2262
Internet SecurityApplication
Affected:= 11.1.2241= 11.1.2245= 11.1.2253= 11.1.2260= 11.1.2261= 11.1.2262
PremierApplication
Affected:= 11.1.2241= 11.1.2245= 11.1.2253= 11.1.2260= 11.1.2261= 11.1.2262
Pro AntivirusApplication
Affected:= 11.1.2241= 11.1.2245= 11.1.2253= 11.1.2260= 11.1.2261= 11.1.2262
Email Server SecurityApplication
Affected:<= 8.0.1609= 8.0.1606
Endpoint ProtectionApplication
Affected:<= 8.0.1609= 8.0.1606
Endpoint Protection PlusApplication
Affected:= 8.0.1606= 8.0.1609

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify an Avast product is installed
    Open Control Panel > Programs and Features, or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for entries containing 'Avast' in the name.
    Affected if No Avast product is found in the installed programs list.
  2. Identify the installed Avast version
    Right-click the Avast system tray icon and select 'About Avast', or check the registry key HKLM\SOFTWARE\Avast Software (or HKLM\SOFTWARE\WOW6432Node\Avast Software) for the 'Version' or 'ProgramVersion' value.
    Affected if Unable to determine the Avast version from the UI or registry.
  3. Compare version against affected list
    Match your installed version number to the following affected versions: 11.1.2241, 11.1.2245, 11.1.2253, 11.1.2260, 11.1.2261, 11.1.2262 for version 11 products; or 8.0.1606, 8.0.1609 (or any version <= 8.0.1609) for version 8 products.
    Affected if The installed version matches one of the affected versions listed in the CVE.
  4. Confirm DeepScreen is enabled
    Open Avast UI, go to Settings > General > DeepScreen (or Settings > Protection > DeepScreen depending on version), and verify the feature is toggled ON.
    Affected if DeepScreen is enabled - this is required for the bypass to be relevant.

You are affected if you have an Avast product installed with a version matching 11.1.2241-11.1.2262 or 8.0.1606-8.0.1609 AND DeepScreen protection is turned on in the settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 8.0.1609
Interim mitigation

Apply vendor-provided patches for affected Avast products when available. Until then, implement additional endpoint detection and network-based monitoring to compensate for the DeepScreen bypass vulnerability.

Fix this in Business Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4025 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data