CVE-2009-0238

Code Injection in Microsoft Office Excel 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1; Excel Viewer 2003 Gold and SP3; Excel Viewer; Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1; and Excel in Microsoft Office 2004 and 2008 for Mac allow remote attackers to execute arbitrary code via a crafted Excel document that triggers an access attempt on an invalid object, as exploited in the wild in February 2009 by Trojan

Verified by Precogs Threat Research
Last Updated: Apr 22, 2026
Base Score
8.8HIGH

Executive Summary

CVE-2009-0238 is a high severity vulnerability affecting appsec. It is classified as Code Injection. This vulnerability is actively being exploited in the wild.

Precogs AI Insight

"Microsoft Office lacks proper bounds checking when parsing specific legacy document formats, creating a classic memory corruption vulnerability. Attackers exploit this via spear-phishing; opening the crafted document overwrites the stack and executes embedded shellcode. The Precogs Binary SAST engine specializes in detecting out-of-bounds memory management without source code."

Exploit Probability (EPSS)
High (74.9%)
Public POC
Available
Exploit Probability
Elevated (52%)
Public POC
Actively Exploited
Affected Assets
appsecCWE-94

What is this vulnerability?

CVE-2009-0238 is categorized as a high Code Injection flaw with a CVSS base score of 8.8. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Microsoft Office Excel 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1; Excel Viewer 2003 Gold and SP3; Excel Viewer; Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1; and Excel in Microsoft Office 2004 and 2008 for Mac allow remote attackers to execute arbitrary code via a crafted Excel document that triggers an access attempt on an invalid object, as exploited in the wild in February 2009 by Trojan.Mdropper.AC.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score8.8 (HIGH)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
PublishedFebruary 25, 2009
Last ModifiedApril 22, 2026
Related CWEsCWE-94, CWE-94

Impact on Systems

Data Exfiltration: Attackers can extract sensitive data from backend databases, configuration files, or internal services.

Authentication Bypass: Exploiting this flaw may allow unauthorized access to protected resources and administrative interfaces.

Lateral Movement: Once initial access is gained, attackers can pivot to internal systems and escalate privileges.

How to Fix and Mitigate CVE-2009-0238

  1. Apply Vendor Patches Immediately: This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  2. Verify Patch Deployment: Confirm all instances are updated using Precogs continuous monitoring.
  3. Review Audit Logs: Investigate historical access logs for indicators of compromise related to this attack surface.
  4. Implement Defense-in-Depth: Deploy WAF rules, network segmentation, and endpoint detection to limit blast radius.

Defending with Precogs AI

Precogs AI Analysis Engine identifies this vulnerability class through semantic code analysis powered by Code Property Graph (CPG) technology, performing inter-procedural taint tracking to detect injection flaws, broken authentication, and insecure data flows across your entire codebase.

Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.

Start scanning with Precogs →

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUntrusted payload via API or file upload
VectorInput passed to a dynamic code evaluation function
Sinkeval(), exec(), or similar unsafe execution sink
ImpactRemote Code Execution (RCE), full system compromise

Vulnerable Code Pattern

# ❌ VULNERABLE: Dynamic code evaluation
def process_data(user_input):
    # Taint sink: arbitrary code execution
    result = eval(user_input)
    return result

Secure Code Pattern

# ✅ SECURE: Safe parsing
import ast
def process_data(user_input):
    # Sanitized parsing: only evaluates literal structures
    result = ast.literal_eval(user_input)
    return result

How Precogs Detects This

Precogs AI Analysis Engine identifies unsafe dynamic code evaluation paths by tracking untrusted data into sinks like eval() and exec().\n

Related Vulnerabilitiesvia CWE-94

Is your system affected?

Precogs AI detects CVE-2009-0238 in compiled binaries, LLMs, and application layers — even without source code access.