dbcve.org
Avast Antivirus HomeApplication · Avast

CVE-2008-1625

MEDIUM · 6.8 CVSS v2.0 Published 2008-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
aavmker4.sys in avast! Home and Professional 4.7 for Windows does not properly validate input to IOCTL 0xb2d60030, which allows local users to gain privileges via certain IOCTL requests.

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 · high confidence

The aavmker4.sys kernel-mode driver in avast! Home and Professional 4.7 for Windows fails to properly validate input when handling IOCTL 0xb2d60030, allowing local attackers to send specially crafted IOCTL requests that can lead to privilege escalation from a low-privileged user context to elevated system privileges.

MitigationUpdate avast! Home and Professional to a version beyond 4.7 that includes the patched driver, or if the product is end-of-life, replace it with a supported antivirus solution that receives regular security updates.

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
Avast Antivirus HomeApplication
Affected:= 4.7.827= 4.7.844= 4.7.869= 4.7.1043= 4.7.1098
Avast Antivirus ProfessionalApplication
Affected:= 4.7.827= 4.7.844= 4.7.1043= 4.7.1098

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:S/C:C/I:C/A:C

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. Check if avast! antivirus is installed
    Open Control Panel > Programs and Features (or Add/Remove Programs) and look for avast! or avast! Antivirus in the list of installed software. Alternatively, check for the presence of avast! installation directory (typically C:\Program Files\Alwil Software\Avast4\)
    Affected if avast! Home or Professional version 4.7.x (specifically 4.7.827, 4.7.844, 4.7.869, 4.7.1043, or 4.7.1098) is installed
  2. Verify the installed avast! version number
    In Programs and Features, right-click avast! and select Properties, or run 'msiexec /x {product code} /qn MSIRESTARTMANAGERCONTROL=0' to check the version. Alternatively, open Task Manager, find an avast! process, right-click and select Properties to view file version. Compare the version to the affected list: 4.7.827, 4.7.844, 4.7.869, 4.7.1043, 4.7.1098
    Affected if The installed version matches any of the listed affected versions (4.7.827, 4.7.844, 4.7.869, 4.7.1043, 4.7.1098)
  3. Confirm the aavmker4.sys driver is present
    Navigate to C:\Windows\System32\drivers\ and verify aavmker4.sys exists. You can also use Command Prompt: 'dir C:\Windows\System32\drivers\aavmker4.sys'
    Affected if The driver file aavmker4.sys exists on the system
  4. Check if the aavmker4.sys driver is loaded
    Open Command Prompt as Administrator and run 'sc query aavmker4' or 'sc query type= driver' to list loaded drivers and find aavmker4 in the output
    Affected if The driver is in a running/loaded state (exploitability requires the driver to be active)
  5. Check driver file version as secondary confirmation
    Right-click aavmmer4.sys in C:\Windows\System32\drivers\, select Properties, then Details tab to view File Version. This may show a version number like 4.7.xxxx that corresponds to the affected avast! version
    Affected if The driver version matches or corresponds to the vulnerable avast! 4.7 build numbers

A system is affected if avast! Home or Professional version 4.7.827, 4.7.844, 4.7.869, 4.7.1043, or 4.7.1098 is installed AND the aavmker4.sys driver is present and loaded.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update avast! Home and Professional to a version beyond 4.7 that includes the patched driver, or if the product is end-of-life, replace it with a supported antivirus solution that receives regular security updates.

Fix this in Avast Antivirus Home Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-1625 — 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-2008-1625 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