CVE-2008-3021

CVE-2008-3021 is a critical-severity vulnerability in Microsoft Office with a CVSS 2.0 base score of 9.3. Its EPSS exploit-prediction score of 36% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-399.

Key facts

Description

Microsoft Office 2000 SP3, XP SP3, and 2003 SP2; Office Converter Pack; and Works 8 do not properly parse the length of a PICT file, which allows remote attackers to execute arbitrary code via a crafted PICT file with an invalid bits_per_pixel field, aka the "PICT Filter Parsing Vulnerability," a different vulnerability than CVE-2008-3018.

Frequently asked questions

What is CVE-2008-3021?
Microsoft Office 2000 SP3, XP SP3, and 2003 SP2; Office Converter Pack; and Works 8 do not properly parse the length of a PICT file, which allows remote attackers to execute arbitrary code via a crafted PICT file with an invalid bits_per_pixel field, aka the "PICT Filter Parsing Vulnerability," a different vulnerability than CVE-2008-3018.
How severe is CVE-2008-3021?
CVE-2008-3021 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2008-3021 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 36% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-3021?
CVE-2008-3021 primarily affects Microsoft Office. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-3021?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2008-3021 published?
CVE-2008-3021 was published on 2008-08-12 and last updated on 2026-06-16.

References

Affected products (5)

More vulnerabilities in Microsoft Office

All CVEs affecting Microsoft Office →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →