avast Antivirus Home up to 4.8.1368.0 Aavmker4.sys input validation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in avast Antivirus Home up to 4.8.1368.0. Impacted is an unknown function of the file Aavmker4.sys. Performing a manipulation results in input validation. This vulnerability is cataloged as CVE-2010-0705. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in avast Antivirus Home up to 4.8.1368.0 (Anti-Malware Software). This affects an unknown functionality of the file Aavmker4.sys. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 02/23/2010 by Tobias Klein (Website). The advisory is shared at vupen.com. This vulnerability is uniquely identified as CVE-2010-0705 since 02/25/2010. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 44876 (avast! Professional Edition < 5.0.418 Local Privilege Escalation), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows. The commercial vulnerability scanner Qualys is able to test this issue with plugin 116916 (Avast! Antivirus "aavmker4.sys" Memory Corruption Vulnerability).

A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (44876), SecurityFocus (BID 38363†), OSVDB (62510†), Secunia (SA38689†) and SecurityTracker (ID 1023644†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.3
VulDB Meta Temp Score: 9.3

VulDB Base Score: 9.3
VulDB Temp Score: 9.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 44876
Nessus Name: avast! Professional Edition < 5.0.418 Local Privilege Escalation
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 800479
OpenVAS Name: Aast! Antivirus aavmker4.sys Denial Of Service Vulnerability (Win)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/11/2010 🔍
02/22/2010 +10 days 🔍
02/22/2010 +0 days 🔍
02/23/2010 +1 days 🔍
02/23/2010 +0 days 🔍
02/23/2010 +0 days 🔍
02/23/2010 +0 days 🔍
02/25/2010 +1 days 🔍
02/25/2010 +0 days 🔍
03/01/2010 +4 days 🔍
03/18/2015 +1843 days 🔍
05/01/2026 +4062 days 🔍

Sourcesinfo

Advisory: vupen.com
Researcher: Tobias Klein
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2010-0705 (🔍)
GCVE (CVE): GCVE-0-2010-0705
GCVE (VulDB): GCVE-100-51969
SecurityFocus: 38363 - Avast! Antivirus 'aavmKer4.sys' Driver IOCTL Handling Local Privilege Escalation Vulnerability
Secunia: 38689
OSVDB: 62510 - avast! Antivirus aavmker4.sys IOCTL Handling Memory Corruption
SecurityTracker: 1023644 - avast! 'aavmker4.sys' IOCTL Processing Bug Lets Local Users Deny Service
Vulnerability Center: 24938 - Avast! Antivirus \x27Aavmker4.sys\x27 Local DoS or Code Execution Vulnerability via IOCTL Request, High

Entryinfo

Created: 03/18/2015 15:15
Updated: 05/01/2026 06:54
Changes: 03/18/2015 15:15 (62), 02/21/2017 17:20 (14), 09/02/2021 18:37 (3), 09/02/2021 18:44 (1), 02/01/2025 17:25 (16), 04/27/2025 06:14 (1), 05/01/2026 06:54 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!