dbcve.org
Avast Antivirus HomeApplication · Avast

CVE-2010-0705

HIGH · 7.2 CVSS v2.0 Published 2010-02-25
Fix available
A fix is available. Upgrade to after 5.0.396.0 or later.
See remediation →
77/100
Remediation priority · High
No privileges 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! 4.8 through 4.8.1368.0 and 5.0 before 5.0.418.0 running on Windows 2000 and XP does not properly validate input to IOCTL 0xb2d60030, which allows local users to cause a denial of service (system crash) or execute arbitrary code to gain privileges via IOCTL requests using crafted kernel addresses that trigger memory corruption.

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 driver in avast! versions 4.8 through 4.8.1368.0 and 5.0 before 5.0.418.0 fails to properly validate input passed to IOCTL 0xb2d60030 on Windows 2000/XP. Local attackers can send crafted IOCTL requests containing malicious kernel addresses that trigger memory corruption, enabling denial of service or privilege escalation to kernel-level execution.

MitigationUpgrade avast! to version 5.0.418.0 or later (or 4.8.1368.1+ for version 4.x). Until patched, limit local untrusted code access and monitor for suspicious IOCTL activity.

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:<= 5.0.396.0= 4.8.1169= 4.8.1195= 4.8.1201= 4.8.1227= 4.8.1229= 4.8.1282= 4.8.1290= 4.8.1296= 4.8.1335= 4.8.1351= 4.8.1368.0
Avast Antivirus ProfessionalApplication
Affected:<= 5.0.396.0= 4.8.1169= 4.8.1195= 4.8.1201= 4.8.1227= 4.8.1229= 4.8.1282= 4.8.1290= 4.8.1296= 4.8.1335= 4.8.1351= 4.8.1356.0

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

AV:L/AC:L/Au:N/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
    Look for avast! in Add/Remove Programs (appwiz.cpl) or check for the presence of C:\Program Files\Alwil Software\Avast4 or C:\Program Files\AVAST Software\Avast directories
    Affected if avast! is not installed on the system, then this CVE does not apply
  2. Determine installed avast! version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Alwil Software\Avast\4.8 (for v4) or HKEY_LOCAL_MACHINE\SOFTWARE\AVAST Software\Avast (for v5), check the Version value; alternatively, right-click the avast! icon in the system tray and select 'About avast!'
    Affected if The installed version matches 4.8.1169, 4.8.1195, 4.8.1201, 4.8.1227, 4.8.1229, 4.8.1282, 4.8.1290, 4.8.1296, 4.8.1335, 4.8.1351, 4.8.1368.0, or any version 5.0.x up to and including 5.0.396.0
  3. Check for vulnerable kernel driver aavmker4.sys
    Open Command Prompt and type 'driverquery /v | findstr aavmker4' or check for the file at C:\Windows\System32\drivers\aavmker4.sys
    Affected if The driver aavmker4.sys is loaded or present on the system
  4. Verify Windows version
    Run 'winver' or check System Properties (sysdm.cpl) to confirm the Windows version
    Affected if The system is running Windows 2000 or Windows XP (the advisory explicitly states these are the affected platforms)

If avast! is installed with a version in the affected list (4.8.1169 through 4.8.1368.0, or 5.0 through 5.0.396.0), the aavmker4.sys driver is present, and the system is Windows 2000 or XP, then the environment is vulnerable to this CVE.

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 5.0.396.0
Interim mitigation

Upgrade avast! to version 5.0.418.0 or later (or 4.8.1368.1+ for version 4.x). Until patched, limit local untrusted code access and monitor for suspicious IOCTL activity.

Fix this in Avast Antivirus Home Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
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,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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