CVE-2010-0479

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

Key facts

Description

Buffer overflow in Microsoft Office Publisher 2002 SP3, 2003 SP3, and 2007 SP1 and SP2 allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Microsoft Office Publisher File Conversion TextBox Processing Buffer Overflow Vulnerability."

Frequently asked questions

What is CVE-2010-0479?
Buffer overflow in Microsoft Office Publisher 2002 SP3, 2003 SP3, and 2007 SP1 and SP2 allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Microsoft Office Publisher File Conversion TextBox Processing Buffer Overflow Vulnerability."
How severe is CVE-2010-0479?
CVE-2010-0479 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2010-0479 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 23% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-0479?
CVE-2010-0479 primarily affects Microsoft Publisher. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-0479?
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-2010-0479 published?
CVE-2010-0479 was published on 2010-04-14 and last updated on 2026-06-16.

References

Affected products (4)

More vulnerabilities in Microsoft Publisher

All CVEs affecting Microsoft Publisher →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →