CVE-2012-5250
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 allowing remote attackers to execute arbitrary code via unspecified vectors. Affects Flash Player versions before 10.3.183.29 and 11.x before 11.4.402.287 on Windows/Mac, before 11.2.202.243 on Linux, and before 11.1.x on Android, plus AIR versions before 3.4.0.2710.
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 in Windows or Mac browserVisit the Adobe version check page at https://www.adobe.com/software/flash/about/ or open a Flash-based content and right-click to select 'About Adobe Flash Player'. The version displays in the dialog.Affected if Version is 10.3.183.25 or lower, or 11.x series below 11.4.402.287 on Windows/Mac
-
Check Adobe Flash Player version on LinuxOn Linux systems, check the version by running 'rpm -q flash-player' or examining the NPAPI plugin file in the browser plugins directory.Affected if Version is below 11.2.202.243 on Linux
-
Check Adobe Flash Player version on AndroidOn Android devices, go to Settings > Applications > Adobe Flash Player (or Settings > Apps > Adobe Flash Player) to view the installed version.Affected if Version is 11.1.x below 11.1.111.19 or 11.1.115.20, or any version 10.x or earlier listed in the affected Android versions
-
Check Adobe AIR version on desktopOn Windows or Mac, open Adobe AIR from the system tray or Start menu and access Help > About Adobe AIR, or check the version in Add/Remove Programs (Windows) or Applications folder (Mac).Affected if Version is 3.4.0.2540 or lower, or any of the older 1.x versions listed in affected AIR versions
-
Verify the vulnerable NPAPI/PPAPI Flash plugin is actually enabledIn web browsers (Chrome, Firefox, Internet Explorer), navigate to the browser's plugins or extensions settings and confirm the Adobe Flash Player plugin is enabled and loaded.Affected if The Flash plugin is enabled and the version falls within the affected ranges above
You are affected if Adobe Flash Player or Adobe AIR is installed and the detected version matches any of the specific version numbers or falls below the safe threshold numbers listed for your platform.
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 · scopedApply vendor patches by updating Adobe Flash Player and Adobe AIR to versions 10.3.183.29+/11.4.402.287+/11.2.202.243+/11.1.111.19+/11.1.115.20+ and 3.4.0.2710+ respectively.
Flash Player 10.3.183.29+ / 11.4.402.287+ (Win/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+
- Identify the exact Adobe Flash Player version installed by navigating to 'About Flash Player' in the player menu or checking the version in the browser's add-ons manager
- Identify the Adobe AIR version by checking Help > About Adobe AIR
- For Windows/Mac Flash Player: Upgrade to version 10.3.183.29 or later (for 10.x) OR version 11.4.402.287 or later (for 11.x)
- For Linux Flash Player: Upgrade to version 10.3.183.29 or later (for 10.x) OR version 11.2.202.243 or later (for 11.x)
- For Android 2.x/3.x Flash Player: Upgrade to version 11.1.111.19 or later
- For Android 4.x Flash Player: Upgrade to version 11.1.115.20 or later
- For Adobe AIR: Upgrade to version 3.4.0.2710 or later
- For Adobe AIR SDK: Upgrade to version 3.4.0.2710 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5250 — 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-5250 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