CVE-2012-5260
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 · uneditedBuffer overflow in Adobe 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than other Flash Player buffer overflow 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 confidenceBuffer overflow vulnerability in Adobe Flash Player and Adobe AIR allows attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple versions across Windows, Mac OS X, Linux, and Android platforms, and is distinct from other buffer overflow 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.
-
Identify installed Adobe Flash Player version on WindowsOpen Control Panel > Programs and Features, look for 'Adobe Flash Player' or check the version via 'about:plugins' in Internet Explorer, or examine the file version of NPSWF32.dll in C:\Windows\System32\Macromed\Flash\Affected if The installed version matches any version listed in the CVE (specific versions or <= 10.3.183.25 for older releases)
-
Identify installed Adobe Flash Player version on Mac OS XCheck /Library/Application Support/Adobe/Flash Player/ for the installer receipt, or run 'ls /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info.plist' and look for CFBundleVersion, or use the Adobe Flash Player settings manager at macromedia.comAffected if The installed version matches any version listed in the CVE (specific versions or <= 10.3.183.25)
-
Identify installed Adobe Flash Player version on LinuxCheck the RPM package with 'rpm -q flash-player' or 'dpkg -l | grep flash', or examine /usr/lib/flash-plugin/libflashplayer.so version infoAffected if The installed version matches any version listed in the CVE (specific versions or <= 10.3.183.25)
-
Identify installed Adobe Flash Player on AndroidOpen Settings > Apps > Adobe Flash Player (or check the app info page) to view the version number, or use 'adb shell pm list packages' to find flash-related packagesAffected if The installed version is <= 11.1.111.16, <= 11.1.115.17, or matches any specific version listed for Android
-
Identify installed Adobe AIR versionOn Windows check Add/Remove Programs for 'Adobe AIR', on Mac check /Applications/Adobe AIR Installer.app, or run 'air -version' from command line if available, or examine the Adobe AIR app propertiesAffected if The installed version is <= 3.4.0.2540 or matches any specific version listed (1.0, 1.0.1, 1.0.8.4990, etc.)
-
Identify installed Adobe AIR SDK versionCheck the AIR SDK installation directory for version file, or run 'adl -version' from the SDK bin folder, or examine the AIR SDK flex_sdk.xml or air_sdk.xml version propertyAffected if The installed AIR SDK version is <= 3.4.0.2540
A user is affected if their installed Adobe Flash Player, Flash Player for Android, Adobe AIR, or AIR SDK version matches any of the specific versions or falls at or below the upper bound versions listed in the 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 or 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); also update Adobe AIR and AIR SDK to 3.4.0.2710 or later.
Flash Player 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 Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system plugin list
- 2. Identify the platform (Windows, Mac OS X, Linux, or Android) and Flash Player branch (10.x or 11.x) to determine the appropriate target version
- 3. For Windows/Mac OS X: Upgrade Flash Player to version 11.4.402.287 or later
- 4. For Linux: Upgrade Flash Player to version 11.2.202.243 or later
- 5. For Android 2.x/3.x: Upgrade Flash Player to version 11.1.111.19 or later
- 6. For Android 4.x: Upgrade Flash Player to version 11.1.115.20 or later
- 7. For Adobe AIR applications: Upgrade Adobe AIR to version 3.4.0.2710 or later
- 8. For developers using Adobe AIR SDK: Upgrade to version 3.4.0.2710 or later
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-5260 — 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-5260 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