CVE-2009-0224: n/a vulnerability

CVE-2009-0224: Microsoft Office PowerPoint 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1 and SP2; PowerPoint Viewer 2003 and...

Microsoft Office PowerPoint 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1 and SP2; PowerPoint Viewer 2003 and 2007 SP1 and SP2; PowerPoint in Microsoft Office 2004 for Mac and 2008 for Mac; Open XML File Format Converter for Mac; Microsoft Works 8.5 and 9.0; and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1 and SP2 do not properly validate PowerPoint files, which allows remote attackers to execute arbitrary code via multiple crafted BuildList records that include ChartBuild containers, which triggers memory corruption, aka "Memory Corruption Vulnerability."

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 04:24 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy Microsoft PowerPoint file-parsing flaw. A malicious presentation could corrupt memory and run attacker-controlled code when opened in affected Office, PowerPoint Viewer, Mac Office, Works, or Compatibility Pack components. Business risk is mainly from old desktops or file-conversion systems still able to open untrusted PowerPoint files. Exposure is likely limited to legacy environments running the affected 2000, 2002, 2003, 2007, Mac Office, Viewer, Works, converter, or Compatibility Pack versions listed in the CVE description. Treat as high priority if legacy Microsoft Office software remains in production. For modern, fully supported Office estates, urgency depends on confirming no listed legacy components persist. Mitigation focus: Review and apply Microsoft MS09-017 guidance for affected systems.; Remove or isolate unsupported affected Office and PowerPoint Viewer versions.; Restrict untrusted PowerPoint files on legacy endpoints where feasible..

Prepared: Jun 28, 2026, 10:45 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2009-0224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 12, 2009, 22:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:6023CVE reference · vdb-entry, signature
MS09-017CVE reference · vendor-advisory, x_refsource_MS

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.