Flash PlayerApplication · Adobe

CVE-2012-5262

HIGH · 10.0 CVSS v2.0 Published 2012-10-09
Fix available
A fix is available. Upgrade to after 11.1.115.17 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer 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 confidence

Buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. The vulnerability affects specific version ranges across Windows, Mac OS X, Linux, and Android platforms. This is a critical memory corruption issue that can be exploited to execute arbitrary code via unspecified vectors.

MitigationUpdate Adobe Flash Player to versions 10.3.183.29, 11.4.402.287, 11.2.202.243, 11.1.111.19, or 11.1.115.20 (platform-dependent) and Adobe AIR to 3.4.0.2710 or later. Remove or disable Flash Player where possible given its end-of-life status.

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
Flash PlayerApplication
Affected:<= 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
Flash Player For AndroidApplication
Affected:<= 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
Adobe AirApplication
Affected:<= 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
Adobe Air SdkApplication
Affected:<= 3.4.0.2540

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Flash Player version on Windows/Mac/Linux
    Locate the Flash Player plugin in the browser or check the version via the Adobe version checker page at get.adobe.com/flashplayer. On Windows, the file npflash32.dll or npflash64.dll in the browser plugins folder often contains version metadata. Use 'reg query' on Windows or inspect the file properties of the Flash plugin binary.
    Affected if The installed version is 10.3.183.25 or earlier, 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.
  2. Check Adobe Flash Player for Android version
    On the Android device, go to Settings > Applications > Adobe Flash Player to view the installed version. Alternatively, use ADB to run 'adb shell pm list packages' to find flash-related packages, then check the package version info.
    Affected if The installed version is 11.1.111.16 or earlier, 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, or 11.1.111.10, or falls within the range 11.1.115.17 or lower.
  3. Check Adobe AIR desktop version
    On Windows, check the installed program via Control Panel > Programs and Features, or inspect the AIR application folder. On Mac, check /Library/Application Support/Adobe/AIR or the version listed in the Air app info. The version is often displayed in the application's properties or can be queried via the AIR runtime.
    Affected if The installed version is 3.4.0.2540 or earlier, 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.
  4. Check Adobe AIR SDK version
    Inspect the AIR SDK installation directory. The version is typically stored in a version file or manifest within the SDK folder, or can be determined by examining the 'AIRSDKConfig.xml' or similar metadata files included with the SDK.
    Affected if The installed SDK version is 3.4.0.2540 or earlier.

A user is affected if any installed Adobe Flash Player, Flash Player for Android, Adobe AIR, or Adobe AIR SDK version matches the specific version numbers or falls within the upper-bounded version ranges listed as affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 11.1.115.17
Interim mitigation

Update Adobe Flash Player to versions 10.3.183.29, 11.4.402.287, 11.2.202.243, 11.1.111.19, or 11.1.115.20 (platform-dependent) and Adobe AIR to 3.4.0.2710 or later. Remove or disable Flash Player where possible given its end-of-life status.

Recommended fix High confidence

Flash Player: 10.3.183.29+ (10.x) or 11.4.402.287+ (11.x) for Windows/Mac; 11.2.202.243+ for Linux; 11.1.111.19+ for Android 2.x/3.x; 11.1.115.20+ for Android 4.x. Adobe AIR/SDK: 3.4.0.2710+

  1. 1. Identify the installed Adobe product: Flash Player (desktop), Flash Player for Android, Adobe AIR, or Adobe AIR SDK
  2. 2. Identify the operating system: Windows, Mac OS X, Linux, or Android
  3. 3. For Flash Player on Windows/Mac OS X: upgrade to version 10.3.183.29 or 11.x to 11.4.402.287 or later
  4. 4. For Flash Player on Linux: upgrade to version 10.3.183.29 or 11.x to 11.2.202.243 or later
  5. 5. For Flash Player on Android 2.x/3.x: upgrade to version 11.1.111.19 or later
  6. 6. For Flash Player on Android 4.x: upgrade to version 11.1.115.20 or later
  7. 7. For Adobe AIR: upgrade to version 3.4.0.2710 or later
  8. 8. For Adobe AIR SDK: upgrade to version 3.4.0.2710 or later
Caveat Flash Player reached end-of-life in December 2020 and should be removed/migrated away from. Consider migrating to HTML5 or alternative technologies.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5262 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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