CVE-2008-0103

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

Key facts

Description

Unspecified vulnerability in Microsoft Office 2000 SP3, Office XP SP3, Office 2003 SP2, and Office 2004 for Mac allows remote attackers to execute arbitrary code via an Office document that contains a malformed object, related to a "memory handling error," aka "Microsoft Office Execution Jump Vulnerability."

Frequently asked questions

What is CVE-2008-0103?
Unspecified vulnerability in Microsoft Office 2000 SP3, Office XP SP3, Office 2003 SP2, and Office 2004 for Mac allows remote attackers to execute arbitrary code via an Office document that contains a malformed object, related to a "memory handling error," aka "Microsoft Office Execution Jump Vulnerability."
How severe is CVE-2008-0103?
CVE-2008-0103 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2008-0103 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 30% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-0103?
CVE-2008-0103 primarily affects Microsoft Office. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-0103?
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-0103 published?
CVE-2008-0103 was published on 2008-02-13 and last updated on 2026-06-16.

References

Affected products (4)

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 →