CVE-2010-0705 Memory corruption in n/a

High 7.2 Published Updated

Local attackers can exploit improper input validation in the avast! kernel driver to cause system crashes or execute arbitrary code with elevated privileges.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2010-0705?

CVE-2010-0705 is a high-severity memory corruption vulnerability in n/a, published on 25 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-20

Which versions are affected by CVE-2010-0705?

It affects 2 products.

Products include Avast Avast Antivirus Home, Avast Avast Antivirus Professional.

How do I fix CVE-2010-0705?

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

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2010-0705 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0705 exists.

Public exploit code: 1 Exploit-DB entry.

Sources

Also known as GHSA-pq8r-7hph-pwj2.

Is CVE-2010-0705 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free