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

Adobe Reader and Acrobat vulnerability

Adobe Reader and Acrobat contain a memory corruption vulnerability (CWE-119) enabling arbitrary code execution or denial of service.

Verdict

Today item — known-exploited.

This vulnerability poses significant risk due to high exploitability (EPSS 0.89557) and confirmed active exploitation. Memory corruption flaws in widely-deployed document readers create direct paths to system compromise.

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

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 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.78581 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Adobe, Reader and Acrobat. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — 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 that triggers a memory corruption flaw when opened in vulnerable Reader or Acrobat versions.
Business
End users opening seemingly legitimate PDF attachments or downloads become compromised without additional user interaction beyond opening the file.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary code with the privileges of the application process, establishing persistence or lateral movement within the target network.
Business
Attackers gain foothold for data exfiltration, malware deployment, or further network reconnaissance across enterprise environments.
3

Lateral reach — past segmentation narrative 3

Attacker
I alternatively trigger a denial of service condition, crashing the Reader or Acrobat process to disrupt document workflows.
Business
Availability impact affects productivity and document-dependent business processes, particularly in organizations relying on PDF handling.
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)
  • 5 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.