CVE-2012-5268
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe Flash Player before 10.3.183.29 and 11.x before 11.4.402.287 on Windows and Mac OS X, before 10.3.183.29 and 11.x before 11.2.202.243 on Linux, before 11.1.111.19 on Android 2.x and 3.x, and before 11.1.115.20 on Android 4.x; Adobe AIR before 3.4.0.2710; and Adobe AIR SDK before 3.4.0.2710 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than other Flash Player memory corruption CVEs listed in APSB12-22.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory corruption vulnerability in Adobe Flash Player and Adobe AIR allows attackers to execute arbitrary code or cause denial of service via unspecified vectors. The vulnerability affects multiple versions across Windows, Mac OS X, Linux, and Android platforms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.3.183.25= 10.1.85.3= 10.1.102.64= 10.2.152.26= 10.2.152.32= 10.2.153.1= 10.2.159.1= 10.3.181.14= 10.3.181.16= 10.3.181.22= 10.3.181.26= 10.3.181.34<= 11.1.111.16= 10.1.106.17= 10.2.157.51= 10.3.186.7= 11.0.1.153= 11.1.102.59= 11.1.111.5= 11.1.111.7= 11.1.111.8= 11.1.111.9= 11.1.111.10<= 11.1.115.17<= 3.4.0.2540= 1.0= 1.0.1= 1.0.8.4990= 1.0.4990= 1.1= 1.1.0.5790= 1.5= 1.5.0.7220= 1.5.1= 1.5.1.8210= 1.5.2<= 3.4.0.2540CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check for Adobe Flash Player on WindowsOpen Control Panel > Programs and Features, look for 'Adobe Flash Player' entry and note the version number displayed, or run 'reg query "HKLM\SOFTWARE\Macromedia\FlashPlayer" /v Version' in Command PromptAffected if version listed is 10.3.183.25 or lower, or matches any of these: 10.1.85.3, 10.1.102.64, 10.2.152.26, 10.2.152.32, 10.2.153.1, 10.2.159.1, 10.3.181.14, 10.3.181.16, 10.3.181.22, 10.3.181.26, 10.3.181.34
-
Check for Adobe Flash Player on MacOpen Safari, go to adobe.com/shockwave/welcome, or check /Library/Application Support/Adobe/Flash Player for version files, or run 'defaults read /Library/Application Support/Adobe/Flash Player'Affected if version is 10.3.183.25 or lower, or matches any of the specific versions listed in the affected range
-
Check for Adobe Flash Player on LinuxRun 'rpm -q flash-plugin' or 'dpkg -l | grep flash' in terminal to retrieve installed package versionAffected if installed version matches the affected Flash Player versions listed
-
Check for Adobe AIR applicationOn Windows check Add/Remove programs for 'Adobe AIR' entry; on Mac check /Applications for Adobe AIR app; run 'air -version' if AIR SDK is installedAffected if Adobe AIR version is 3.4.0.2540 or lower, or matches any of these: 1.0, 1.0.1, 1.0.8.4990, 1.0.4990, 1.1, 1.1.0.5790, 1.5, 1.5.0.7220, 1.5.1, 1.5.1.8210, or 1.5.2
-
Check for Adobe AIR SDKIf you have Adobe AIR SDK installed, run 'air -version' or check the SDK version file in the installation directoryAffected if AIR SDK version is 3.4.0.2540 or lower
Your environment is affected if any installed Adobe Flash Player or Adobe AIR version matches the specific version numbers or falls within the version ranges listed as vulnerable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Adobe Flash Player to versions 10.3.183.29/11.4.402.287 (Windows/Mac), 11.2.202.243 (Linux), 11.1.111.19 (Android 2.x/3.x), or 11.1.115.20 (Android 4.x); update Adobe AIR to 3.4.0.2710 or later.
Flash Player 10.3.183.29/11.4.402.287 (Windows/Mac), 11.2.202.243 (Linux), 11.1.111.19 (Android 2.x/3.x), 11.1.115.20 (Android 4.x); Adobe AIR 3.4.0.2710; Adobe AIR SDK 3.4.0.2710
- 1. Identify the currently installed Flash Player or Adobe AIR version by navigating to About Flash Player (right-click on SWF content) or checking the system's installed programs
- 2. Determine the appropriate fixed version based on your platform: Windows/Mac OS X users need Flash Player 10.3.183.29 or 11.4.402.287; Linux users need Flash Player 10.3.183.29 or 11.2.202.243; Android 2.x/3.x users need Flash Player 11.1.111.19; Android 4.x users need Flash Player 11.1.115.20
- 3. For Adobe AIR or Adobe AIR SDK, download version 3.4.0.2710
- 4. Download the appropriate Flash Player installer from the official Adobe website (archived versions)
- 5. Close all browser instances and any applications using Flash Player or AIR
- 6. Run the installer with administrator privileges
- 7. Restart the browser or application
- 8. Verify the installed version matches the target fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-5268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data