Threats / Adobe / CVE-2012-2034
CVE-2012-2034
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Adobe Flash Player vulnerability
Adobe Flash Player memory corruption vulnerability enabling remote code execution or denial-of-service attacks.
Verdict
Today item — known-exploited.
Memory corruption flaw in Flash Player permits attackers to execute arbitrary code or crash the application through crafted content, with confirmed exploitation in the wild.
CISA KEV Yes · 2022-03-284EPSS 0.078 (verify live)5CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1 independent public report 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-28).
Probability (EPSS)
EPSS 0.078 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Adobe, Flash Player. 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 3579 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.
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 malicious Flash content exploiting the memory corruption to achieve code execution on a target system.
Business
Attackers gain unauthorized access to systems running vulnerable Flash Player, enabling data theft, malware installation, or lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit-laden Flash file via email, compromised website, or advertisement to reach end users.
Business
Enterprise endpoints become compromised without user awareness, expanding attack surface and increasing breach risk.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence or escalate privileges post-exploitation using the initial code execution foothold.
Business
Attackers maintain long-term access to critical systems, enabling espionage, data exfiltration, or sabotage operations.
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