CVE-2009-3459 Google Chronicle · YARA-L

Detect Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459) in Google Chronicle

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.

MITRE ATT&CK

Tactic
Initial Access Execution Defense Evasion

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2009_3459_adobe_reader_heap_overflow {
  meta:
    author = "df00tech Detection Engineering"
    description = "Detects CVE-2009-3459 Adobe Acrobat/Reader heap overflow exploitation via child process spawning or executable drop"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://nvd.nist.gov/vuln/detail/CVE-2009-3459"
    mitre_attack = "T1203"

  events:
    $e1.metadata.event_type = "PROCESS_LAUNCH"
    $e1.principal.process.file.full_path = /(?i)(AcroRd32\.exe|Acrobat\.exe|AcroBroker\.exe)/
    $e1.target.process.file.full_path = /(?i)(cmd\.exe|powershell\.exe|wscript\.exe|cscript\.exe|mshta\.exe|rundll32\.exe|regsvr32\.exe)/
    $host = $e1.principal.hostname

  condition:
    $e1
}
critical severity high confidence

Chronicle YARA-L rule detecting Adobe Reader or Acrobat spawning known shell interpreters, a primary indicator of heap overflow exploitation for CVE-2009-3459.

Data Sources

Chronicle UDMWindows Event Logs via Chronicle forwarderSysmon via Chronicle

Required Tables

UDM Process Events

False Positives & Tuning

  • Adobe Acrobat Pro with JavaScript actions that legitimately call system utilities
  • IT-managed PDF workflows using Adobe Reader as a document rendering engine
  • Security awareness tools that open malicious PDFs in sandboxes with Reader

Other platforms for CVE-2009-3459


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