CVE-2009-3523 Memory corruption in n/a

Medium 6.9 Published 1 Oct 2009 Updated 7 Aug 2024

Local attackers can exploit improper IOCTL validation in the avast! kernel driver to trigger memory corruption and escalate 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-2009-3523?

CVE-2009-3523 is a medium-severity memory corruption vulnerability in n/a, published on 1 Oct 2009. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

aavmKer4.sys in avast! Home and Professional for Windows before 4.8.1356 does not properly validate input to IOCTLs (1) 0xb2d6000c and (2) 0xb2d60034, which allows local users to gain privileges via IOCTL requests using crafted kernel addresses that trigger memory corruption, a different vulnerability than CVE-2008-1625.

Weakness: CWE-20

Which versions are affected by CVE-2009-3523?

It affects 2 products.

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

How do I fix CVE-2009-3523?

No fix has been published for CVE-2009-3523 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-2009-3523 being exploited?

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

Public exploit code: 1 Exploit-DB entry.

Sources

Also known as GHSA-65m7-qc75-24vh.