Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2010-2572

Microsoft PowerPoint Buffer Overflow Vulnerability

Microsoft PowerPoint

Buffer overflow in Microsoft PowerPoint 2002 SP3 and 2003 SP3 allows remote attackers to execute arbitrary code via a crafted PowerPoint 95 document, aka "PowerPoint Parsing Buffer Overflow Vulnerability."

CVSS
7.8
HIGH
EPSS
58.6%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
10 Nov 2010
CWE-120

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 8 June 2022. US federal agencies were required to remediate it by 22 June 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 58.6%, which is higher than 99.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2010-2572 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2010-2572.

What does CVE-2010-2572 affect?

CVE-2010-2572 affects Microsoft PowerPoint. Buffer overflow in Microsoft PowerPoint 2002 SP3 and 2003 SP3 allows remote attackers to execute arbitrary code via a crafted PowerPoint 95 document, aka "PowerPoint Parsing Buffer Overflow Vulnerability."

How severe is CVE-2010-2572?

CVE-2010-2572 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 58.6%, higher than 99.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 June 2022.

How should organisations respond to CVE-2010-2572?

Apply the vendor patch for Microsoft PowerPoint as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.