Threats / Adobe / CVE-2013-3346
CVE-2013-3346
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-034EPSS 0.78581 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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).
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
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Adobe, Reader and Acrobat. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3107 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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