Detect Adobe Acrobat and Reader Heap-Based Buffer Overflow (CVE-2009-3459) in Elastic Security
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
Elastic Detection Query
sequence by host.name with maxspan=2m
[process where process.name : ("AcroRd32.exe", "Acrobat.exe", "AcroBroker.exe") and event.type == "start"]
[any where
(
(event.category == "process" and process.parent.name : ("AcroRd32.exe", "Acrobat.exe", "AcroBroker.exe") and
process.name : ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe"))
or
(event.category == "network" and process.name : ("AcroRd32.exe", "Acrobat.exe") and
not destination.ip : ("10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16", "127.0.0.0/8"))
or
(event.category == "file" and process.name : ("AcroRd32.exe", "Acrobat.exe") and
file.extension : ("exe", "dll", "bat", "ps1", "vbs") and
file.path : ("*\\Temp\\*", "*\\AppData\\*", "*\\Public\\*"))
)
]EQL sequence rule detecting Adobe Reader launch followed within 2 minutes by child process spawning, external network connection, or executable file creation — consistent with heap overflow exploitation.
Data Sources
Required Tables
False Positives & Tuning
- Adobe Acrobat Pro plugins that legitimately spawn helper processes
- Corporate DLP agents that hook into Adobe Reader network calls
- Automated document scanning workflows invoking Adobe Reader headlessly
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.
- 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.
- 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.
- 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.
- 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.
References (3)
- https://www.cisa.gov/news-events/alerts/2009/10/13/adobe-reader-and-acrobat-vulnerabilities
- https://web.archive.org/web/20120324170253/http://www.adobe.com/support/security/bulletins/apsb09-15.html#:~:text=CVE%2D2009%2D3459).-,NOTE%3A,-There%20are%20reports
- https://nvd.nist.gov/vuln/detail/CVE-2009-3459
Unlock Pro Content
Get the full detection package for CVE-2009-3459 including response playbook, investigation guide, and atomic red team tests.