CVE-2012-2035
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 · uneditedStack-based buffer 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 confidenceStack-based buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple platforms including Windows, Mac OS X, Linux, and Android across various version ranges.
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.
-
Detect installed Adobe Flash Player version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FlashPlayer\CurrentVersion, or check file properties of npflash32.dll or NPSWF32.dll in the System32 or SysWOW64 foldersAffected if Version number is 11.2.202.235 or lower, 11.1.115.8 or lower, or 11.1.111.9 or lower
-
Detect installed Adobe Flash Player version on LinuxRun 'rpm -q flash-plugin' or 'dpkg -l | grep flash' to query the package manager, or check /usr/lib/flash-plugin/ for installed filesAffected if Version number is 11.2.202.235 or lower
-
Detect installed Adobe Flash Player version on Mac OS XRun 'defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion' or check the plugin in /Library/Internet Plug-Ins/Affected if Version number is 11.2.202.235 or lower, 11.1.115.8 or lower, or 11.1.111.9 or lower
-
Detect installed Adobe AIR versionOn Windows check Add/Remove Programs for Adobe AIR or examine the version via the AIR app's properties; on Mac check /Applications/Adobe AIR Installer.app; on Linux run 'rpm -q adobe-air' or 'dpkg -l | grep air'Affected if Version number is 3.2.0.2070 or lower
-
Check for Flash or AIR on Red Hat Enterprise Linux systemsRun 'rpm -qa | grep -i flash' or 'rpm -qa | grep -i air' to list installed packages, or check if the flash-plugin or adobe-air packages are presentAffected if Flash or AIR packages are installed on RHEL 5.0, 5.x, 6.0, 6.x, 6.2, or derivative versions (Eus, Aus)
-
Check for Flash or AIR on OpenSUSE systemsRun 'rpm -qa | grep -i flash' or 'rpm -qa | grep -i air' to list installed packagesAffected if Flash or AIR packages are installed on OpenSUSE 11.4 or 12.1
Your environment is affected if Adobe Flash Player version is <= 11.2.202.235, <= 11.1.115.8, or <= 11.1.111.9; or Adobe AIR version is <= 3.2.0.2070; and the software is installed on the listed Red Hat or OpenSUSE versions.
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.20/11.3.300.257 (Windows/Mac), 11.2.202.236 (Linux), 11.1.111.10 (Android 2.x/3.x), or 11.1.115.9 (Android 4.x), and Adobe AIR to 3.3.0.3610 or later to remediate this vulnerability.
Flash Player 11.2.202.236 (Linux) / 11.3.300.257 (Windows/Mac) / Adobe AIR 3.3.0.3610
- Identify the exact Adobe Flash Player version installed on the system
- For Linux systems: upgrade to Flash Player 11.2.202.236 or later
- For Windows/Mac OS X systems: upgrade to Flash Player 11.3.300.257 or later (or 10.3.183.20 for legacy 10.x)
- For Adobe AIR: upgrade to version 3.3.0.3610 or later
- On Red Hat Enterprise Linux systems: run 'yum update flash-plugin' or obtain updates via Red Hat Network
- On openSUSE systems: run 'zypper update flash-player' or obtain updates via package manager
- Restart any running instances of Flash Player or browser after applying the update
- Verify the installed version matches or exceeds the fixed release versions listed
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-2035 — 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-2035 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