Menu

Star on GitHub · 3.2k

CVE-2006-1355

7.2 · HIGH

avast!

Published Mar 22, 2006alwilEPSS 0.39%

Overview

CVE-2006-1355 is a high-severity vulnerability affecting alwil avast_antivirus. It was published on March 22, 2006 and has a CVSS 2.0 base score of 7.2 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

avast! Antivirus 4.6.763 and earlier sets "BUILTIN\Everyone" permissions to critical system files in the installation folder, which allows local users to gain privileges or disable protection by modifying those files.

Remediation

Check the references section for vendor advisories and patches from alwil. Update avast_antivirus to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
alwilavast_antivirus0Affected

Frequently asked questions

What is CVE-2006-1355?

CVE-2006-1355 is a high-severity vulnerability affecting alwil avast_antivirus. It was published on March 22, 2006 and has a CVSS 2.0 base score of 7.2 (HIGH).

How severe is CVE-2006-1355?

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2006-1355?

Check the references section for vendor advisories and patches from alwil. Update avast_antivirus to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2006-1355?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-1355 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2006

View all