CVE-2009-3459

Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459)

Detects exploitation of a heap-based buffer overflow vulnerability in Adobe Acrobat and Reader (CVE-2009-3459). This CISA KEV vulnerability allows attackers to execute arbitrary code via a crafted PDF file. Exploitation typically results in AcroRd32.exe or Acrobat.exe spawning unexpected child processes, making unusual network connections, or writing executable payloads to disk.

Vulnerability Intelligence

KEV — Known Exploited

What is CVE-2009-3459 Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459)?

Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459) (CVE-2009-3459) maps to the Initial Access and Execution and Defense Evasion tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, Microsoft Sentinel DeviceProcessEvents, Microsoft Sentinel DeviceNetworkEvents, Microsoft Sentinel DeviceFileEvents. The queries below are rated critical severity at high confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Defense Evasion
Microsoft Sentinel / Defender
kusto
let suspiciousChildren = dynamic(["cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "svchost.exe", "explorer.exe"]);
let adobeProcs = dynamic(["AcroRd32.exe", "Acrobat.exe", "AcroBroker.exe"]);
union
(
  DeviceProcessEvents
  | where InitiatingProcessFileName has_any (adobeProcs)
  | where FileName has_any (suspiciousChildren)
  | project TimeGenerated, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, FolderPath
  | extend DetectionReason = "Adobe Reader/Acrobat spawned suspicious child process"
),
(
  DeviceNetworkEvents
  | where InitiatingProcessFileName has_any (adobeProcs)
  | where RemotePort in (80, 443, 445, 4444, 8080, 8443)
  | where RemoteIPType != "Private"
  | project TimeGenerated, DeviceName, AccountName, InitiatingProcessFileName, RemoteIP, RemotePort, RemoteUrl
  | extend DetectionReason = "Adobe Reader/Acrobat initiated outbound network connection"
),
(
  DeviceFileEvents
  | where InitiatingProcessFileName has_any (adobeProcs)
  | where FileName endswith ".exe" or FileName endswith ".dll" or FileName endswith ".bat" or FileName endswith ".ps1"
  | where FolderPath has_any ("\\Temp\\", "\\AppData\\", "\\Public\\", "\\Downloads\\")
  | project TimeGenerated, DeviceName, AccountName, InitiatingProcessFileName, FileName, FolderPath
  | extend DetectionReason = "Adobe Reader/Acrobat dropped executable to writable path"
)
| summarize count() by TimeGenerated, DeviceName, AccountName, DetectionReason
| sort by TimeGenerated desc

Detects Adobe Acrobat or Reader spawning suspicious child processes, making external network connections, or writing executables to writable directories — all indicators of heap overflow exploitation.

critical severity high confidence

Data Sources

Microsoft Defender for Endpoint Microsoft Sentinel DeviceProcessEvents Microsoft Sentinel DeviceNetworkEvents Microsoft Sentinel DeviceFileEvents

Required Tables

DeviceProcessEvents DeviceNetworkEvents DeviceFileEvents

False Positives

  • Legitimate Adobe Reader updates or plugin installers may spawn child processes
  • Enterprise PDF workflows that trigger scripted post-processing via Adobe Reader
  • IT automation tools opening PDFs as part of document conversion pipelines

Sigma rule & cross-platform mapping

The detection logic for Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459) (CVE-2009-3459) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate Adobe Reader Spawning cmd.exe

    Expected signal: Sysmon Event ID 1: process creation with ParentImage matching AcroRd32.exe and Image matching cmd.exe; DeviceProcessEvents in Defender with InitiatingProcessFileName=AcroRd32.exe and FileName=cmd.exe.

  2. Test 2Simulate Adobe Reader Writing Executable to Temp

    Expected signal: Sysmon Event ID 11: TargetFilename=C:\Temp\payload.exe, Image matching AcroRd32.exe; DeviceFileEvents in Defender with InitiatingProcessFileName=AcroRd32.exe and FileName=payload.exe.

  3. Test 3Simulate Adobe Reader Making Outbound Network Connection

    Expected signal: Sysmon Event ID 3: Image matching AcroRd32.exe, DestinationIp=93.184.216.34, DestinationPort=80; DeviceNetworkEvents in Defender with InitiatingProcessFileName=AcroRd32.exe and non-RFC1918 RemoteIP.

  4. Test 4Open Malicious PDF in Sandboxed Adobe Reader (Lab Only)

    Expected signal: Heap spray artifacts in AcroRd32.exe memory; child process creation events; potential shellcode execution visible in memory forensics; network connection attempt if payload is weaponized.

Unlock Pro Content

Get the full detection package for CVE-2009-3459 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections