How severe is CVE-2009-3524?

CVE-2009-3524 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2009-3524 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2009-3524?

CVE-2009-3524 primarily affects Avast Avast Antivirus Home. In total, 29 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2009-3524?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2009-3524 published?

CVE-2009-3524 was published on 2009-10-01 and last updated on 2026-06-16.

CVE-2009-3524

CVE-2009-3524 is a high-severity vulnerability in Avast Avast Antivirus Home with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.2)
EPSS exploit prediction: 0% (30th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Avast Avast Antivirus Home
Published: 2009-10-01
Last modified: 2026-06-16

Description

Unspecified vulnerability in ashWsFtr.dll in avast! Home and Professional for Windows before 4.8.1356 has unknown impact and local attack vectors.

Frequently asked questions

What is CVE-2009-3524?: Unspecified vulnerability in ashWsFtr.dll in avast! Home and Professional for Windows before 4.8.1356 has unknown impact and local attack vectors.
How severe is CVE-2009-3524?: CVE-2009-3524 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2009-3524 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-3524?: CVE-2009-3524 primarily affects Avast Avast Antivirus Home. In total, 29 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-3524?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-3524 published?: CVE-2009-3524 was published on 2009-10-01 and last updated on 2026-06-16.

References

Affected products (29)

cpe:2.3:a:avast:avast_antivirus_home:*:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.7.827:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.7.844:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.7.869:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.7.1043:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.7.1098:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1169:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1195:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1201:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1227:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1229:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1282:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1290:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1296:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_home:4.8.1335:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:*:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.7.827:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.7.844:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.7.1043:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.7.1098:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1169:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1195:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1201:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1227:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1229:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1282:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1290:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1296:*:windows:*:*:*:*:*
cpe:2.3:a:avast:avast_antivirus_professional:4.8.1335:*:windows:*:*:*:*:*

More vulnerabilities in Avast Avast Antivirus Home

CVE-2007-1673 — High (CVSS 7.8): unzoo.c, as used in multiple products including AMaViS 2.4.1 and earlier, allows remote attackers to cause a denial of…
CVE-2010-0705 — High (CVSS 7.2): 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…
CVE-2009-4049 — High (CVSS 7.2): Heap-based buffer overflow in aswRdr.sys (aka the TDI RDR driver) in avast! Home and Professional 4.8.1356.0 allows…
CVE-2009-3522 — High (CVSS 7.2): Stack-based buffer overflow in aswMon2.sys in avast! Home and Professional for Windows 4.8.1351, and possibly other…
CVE-2009-3523 — Medium (CVSS 6.9): aavmKer4.sys in avast! Home and Professional for Windows before 4.8.1356 does not properly validate input to IOCTLs (1)…
CVE-2008-1625 — Medium (CVSS 6.8): aavmker4.sys in avast! Home and Professional 4.7 for Windows does not properly validate input to IOCTL 0xb2d60030,…

All CVEs affecting Avast Avast Antivirus Home →