Skip to main content
Mallory
CriticalVulnerability

CVE-2012-4167: Integer Overflow in Adobe Flash Player and AIR (CVE-2012-4167)

Published Aug 21, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS9.2%95th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Adobe
IdentifiersCVE-2012-4167CWE-190

CVE-2012-4167 is an integer overflow vulnerability in Adobe Flash Player (prior to 10.3.183.23 and 11.x before 11.4.402.265 on Windows and Mac OS X, prior to 10.3.183.23 and 11.x before 11.2.202.238 on Linux, prior to 11.1.111.16 on Android 2.x/3.x, and prior to 11.1.115.17 on Android 4.x) and Adobe AIR (prior to 3.4.0.2540 and AIR SDK prior to 3.4.0.2540). The vulnerability allows attackers to execute arbitrary code via unspecified vectors, likely by exploiting the integer overflow to corrupt memory and gain control of program execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code in the context of the user running the vulnerable Flash Player or AIR application. This can lead to full compromise of the affected system, including installation of malware, data theft, or further exploitation.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable or uninstall Flash Player and AIR where feasible, or use browser security features to restrict Flash content to trusted sites only. Employ endpoint security solutions to detect and block exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade Adobe Flash Player to version 10.3.183.23 or 11.4.402.265 (Windows/Mac), 10.3.183.23 or 11.2.202.238 (Linux), 11.1.111.16 (Android 2.x/3.x), or 11.1.115.17 (Android 4.x). Upgrade Adobe AIR and AIR SDK to version 3.4.0.2540 or later. Apply all relevant security patches provided by Adobe.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdobeAirapplication
AdobeAir Sdkapplication
AdobeFlash Playerapplication
FAQ

Frequently asked questions

Is CVE-2012-4167 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2012-4167?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2012-4167.
Is there a patch for CVE-2012-4167?
Upgrade Adobe Flash Player to version 10.3.183.23 or 11.4.402.265 (Windows/Mac), 10.3.183.23 or 11.2.202.238 (Linux), 11.1.111.16 (Android 2.x/3.x), or 11.1.115.17 (Android 4.x). Upgrade Adobe AIR and AIR SDK to version 3.4.0.2540 or later.
What products are affected by CVE-2012-4167?
Adobe Air, Adobe Air Sdk, and Adobe Flash Player.
How severe is CVE-2012-4167?
CVE-2012-4167 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 9.2% (95th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.