basicsecurity.net
Proof, not just disclosure.
Threats / Adobe / CVE-2013-0641
CVE-2013-0641 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Adobe Reader vulnerability

A buffer overflow vulnerability in Adobe Reader enables remote code execution when processing malicious documents, allowing attackers to execute arbitrary code with user privileges.

Verdict

Today item — known-exploited.

This vulnerability poses significant risk due to active exploitation in the wild. The buffer overflow in a widely-deployed PDF reader permits unauthenticated remote code execution, requiring only that a user open a crafted document.

CISA KEV Yes · 2022-03-033EPSS 0.32449 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.32449 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Adobe, Reader. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-120 Buffer Copy without Size Check — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious PDF document containing specially-formatted data that overflows a buffer in Adobe Reader's parsing logic.
Business
End users face direct compromise of their systems and data when opening email attachments or downloading files from untrusted sources.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I distribute the malicious PDF through email, web downloads, or document sharing platforms to reach target victims.
Business
Organizations experience potential data breaches, intellectual property theft, and operational disruption from compromised employee systems.
3

Lateral reach — past segmentation narrative 3

Attacker
Upon successful exploitation, I gain code execution in the context of the user running Adobe Reader, allowing me to install malware or establish persistence.
Business
Enterprises must respond to security incidents, conduct forensics, notify affected parties, and remediate compromised endpoints at significant cost.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 7 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by adobe (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by adobeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.