CVE-2012-5263
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 AIR allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. Affects multiple platforms (Windows, Mac OS X, Linux, Android) and is distinct from other memory corruption CVEs in APSB12-22.
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 Adobe Flash Player version on Windows or MacOpen a browser, right-click on any Flash content (such as a video), select 'About Adobe Flash Player' or visit Adobe's version check page. Alternatively, check the Windows registry at HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion or on Mac at /Library/Application Support/Adobe/Flash Player/Affected if The displayed version is 10.3.183.25 or lower; or matches any of these specific versions: 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, or 10.3.181.34
-
Check Adobe Flash Player version on LinuxOpen a terminal and run: rpm -q flash-plugin (for RPM-based distros) or dpkg -l flashplugin-installer (for Debian-based distros). Alternatively, check /usr/lib/flash-plugin/libflashplayer.so or the browser plugin directory.Affected if The installed version is 10.3.183.25 or lower; or matches any of the specific affected versions listed for Flash Player.
-
Check Adobe Flash Player for Android versionOn the Android device, go to Settings > Applications > Manage Applications > Adobe Flash Player, or check the version displayed in the app details.Affected if The version is 11.1.111.16 or lower; or matches any of these specific versions: 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, or 11.1.115.17 or lower.
-
Check Adobe AIR version on desktopOn Windows, go to Control Panel > Programs and Features > Adobe AIR, or right-click the Adobe AIR application icon and select 'About Adobe AIR'. On Mac, navigate to /Applications/Adobe AIR Installer.app/Contents/MacOS/Adobe AIR and run it with -version, or check the version in the application info.Affected if The version is 3.4.0.2540 or lower; or matches any of these specific versions: 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, or 1.5.1.8210.
-
Check Adobe AIR SDK versionNavigate to the AIR SDK installation directory and open the readme.txt or version.txt file, or run: adt -version from the command line within the SDK bin folder.Affected if The AIR SDK version is 3.4.0.2540 or lower.
If any installed Adobe Flash Player, Flash Player for Android, Adobe AIR, or AIR SDK version matches or falls within the affected ranges listed above, the environment is vulnerable to this CVE.
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 version 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/AIR SDK to 3.4.0.2710 or later.
Flash Player: 10.3.183.29+ (10.x) or 11.4.402.287+ (11.x Windows/Mac), 11.2.202.243+ (11.x Linux), 11.1.111.19+ (Android 2.x/3.x), 11.1.115.20+ (Android 4.x); Adobe AIR/SDK: 3.4.0.2710+
- 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the Help menu or visiting adobe.com/software/flash/about
- 2. Identify the installed Adobe AIR version by checking the application's properties or using the AIR version detector
- 3. For Flash Player on Windows/Mac: Download and install Flash Player 10.3.183.29 or later for 10.x branch, or 11.4.402.287 or later for 11.x branch
- 4. For Flash Player on Linux: Download and install Flash Player 11.2.202.243 or later
- 5. For Flash Player on Android 2.x/3.x: Download and install version 11.1.111.19 or later
- 6. For Flash Player on Android 4.x: Download and install version 11.1.115.20 or later
- 7. For Adobe AIR: Uninstall current version, then download and install Adobe AIR 3.4.0.2710 or later from adobe.com
- 8. For Adobe AIR SDK: Download and install Adobe AIR SDK 3.4.0.2710 or later from adobe.com
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5263 — 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-5263 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