CVE-2012-2036
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 · uneditedInteger overflow in Adobe Flash Player before 10.3.183.20 and 11.x before 11.3.300.257 on Windows and Mac OS X; before 10.3.183.20 and 11.x before 11.2.202.236 on Linux; before 11.1.111.10 on Android 2.x and 3.x; and before 11.1.115.9 on Android 4.x, and Adobe AIR before 3.3.0.3610, allows attackers to execute arbitrary code via unspecified vectors.
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 confidenceInteger overflow vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The integer overflow enables memory corruption that can be leveraged for code execution.
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= 5.0= 6.0= 6.2= 5.0= 6.0= 6.2= 5.0= 6.0<= 11.2.202.235<= 11.1.115.8<= 11.1.111.9<= 3.2.0.2070= 11.4= 12.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 if Adobe Flash Player is installedOn Windows, check for flash player in browser plugins (Chrome: chrome://plugins, Firefox: Add-ons > Plugins) or look for NPSWF32.dll in System32 or SysWOW64. On Linux, check /usr/lib/flash-plugin or /usr/lib64/flash-plugin directory. On Mac, check /Library/Internet Plug-Ins/Affected if Flash Player is found on the system
-
Determine Flash Player version on WindowsFor IE/ActiveX: Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. For Chrome PPAPI: Right-click on Flash in chrome://plugins and view version. For Firefox NPAPI: Go to Add-ons > Plugins and view version.Affected if Version is 11.2.202.235 or lower, 11.1.115.8 or lower, or 11.1.111.9 or lower
-
Determine Flash Player version on LinuxRun: rpm -q flash-plugin or dpkg -l | grep flash or check /usr/lib/flash-plugin/version.text. For browser plugins, check about:plugins in Firefox or chrome://plugins in Chrome.Affected if Version is 11.2.202.235 or lower, 11.1.115.8 or lower, or 11.1.111.9 or lower
-
Check for Adobe AIR installationOn Windows: Check registry HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR for Version string, or look in Program Files. On Mac: Check /Applications/Adobe AIR Installer.app. On Linux: Check /opt/adobe-air-sdk or run dpkg/rpm query for adobe-air.Affected if Adobe AIR is installed with version 3.2.0.2070 or lower
-
Verify Adobe AIR versionOn Windows, read the Version value from registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR or check the AIR app's version info. On Mac, right-click Adobe AIR Installer.app > Get Info. On Linux, check the version from the package manager query.Affected if Version is 3.2.0.2070 or lower
The system is affected if Adobe Flash Player version is 11.2.202.235 or lower, 11.1.115.8 or lower, 11.1.111.9 or lower, OR Adobe AIR version is 3.2.0.2070 or lower.
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 · scopedUpgrade Adobe Flash Player to version 10.3.183.20+, 11.x to 11.3.300.257+ (Windows/Mac), 11.2.202.236+ (Linux), or 11.1.111.10+/11.1.115.9+ (Android). Upgrade Adobe AIR to 3.3.0.3610+. Remove unused Flash installations.
Flash Player 11.2.202.236 (Linux) or later; Adobe AIR 3.3.0.3610 or later
- 1. Identify the installed Adobe Flash Player version: rpm -q flash-plugin or check the version in the browser's plugin manager
- 2. For Enterprise Linux systems: Run 'yum update flash-plugin' to receive the patched version from RHN
- 3. For OpenSUSE systems: Run 'zypper update flash-player' or 'zypper patch' to apply security updates
- 4. Restart all web browsers after the update completes
- 5. Verify the installed version matches or exceeds the fixed release: 11.2.202.236 for Linux Flash Player, or 3.3.0.3610 for Adobe AIR
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2036 — 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-2036 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