CVE-2012-2039
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 · uneditedAdobe 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 or cause a denial of service (NULL pointer dereference) 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 confidenceAdobe Flash Player and Adobe AIR contain a vulnerability allowing remote attackers to execute arbitrary code or cause a denial of service via NULL pointer dereference. The vulnerability affects specific version ranges across Windows, Mac OS X, Linux, and Android platforms.
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 Adobe Flash Player version on WindowsOpen a browser and navigate to 'About Flash Player' (right-click on Flash content), or check registry key: HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersionAffected if Version number is less than or equal to 11.2.202.235, 11.1.115.8, or 11.1.111.9 depending on the release line
-
Check Adobe Flash Player version on LinuxRun command: rpm -q flash-player or dpkg -l | grep flash, or check /usr/lib/flash-plugin/ for the installation directory and read version infoAffected if Version number is less than or equal to 11.2.202.235
-
Check Adobe Flash Player version on macOSCheck /Library/Application Support/Adobe/Flash Player/ or use the Flash Player About panel in Safari/ChromeAffected if Version number is less than or equal to 11.2.202.235, 11.1.115.8, or 11.1.111.9 depending on the release line
-
Check Adobe AIR version on WindowsOpen Windows Control Panel > Programs and Features, or check registry: HKLM\SOFTWARE\Adobe\AIR\VersionInfoAffected if Version is less than or equal to 3.2.0.2070
-
Check Adobe AIR version on Linux/MacRun command: adl -version or check the application's version info within the AIR runtime directoryAffected if Version is less than or equal to 3.2.0.2070
-
Verify if Flash Player is installed via system packages on RHEL/CentOSRun: rpm -qa | grep -i flash or yum list installed | grep flashAffected if Any Flash Player package is installed on RHEL 5.0, 6.0, or 6.2 (these versions bundled vulnerable Flash)
The environment is affected if Adobe Flash Player version is at or below 11.2.202.235 (Linux), 11.1.115.8, or 11.1.111.9, or Adobe AIR is at or below 3.2.0.2070.
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 or later (Windows/Mac), 11.2.202.236 or later (Linux), or 11.1.111.10+ (Android 2.x/3.x) / 11.1.115.9+ (Android 4.x); update Adobe AIR to 3.3.0.3610 or later. Note: Adobe Flash Player reached end-of-life in December 2020 and should be removed rather than updated where possible.
Adobe Flash Player 11.2.202.236 or later for Linux; Adobe AIR 3.3.0.3610 or later
- 1. Verify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the Adobe website or checking the system package manager
- 2. For Red Hat Enterprise Linux systems, use 'rpm -q flash-plugin' to check the installed version
- 3. For OpenSUSE systems, use 'rpm -q flash-player' or check via YaST package manager
- 4. Uninstall the vulnerable Flash Player version using the system package manager (e.g., 'yum remove flash-plugin' or 'zypper remove flash-player')
- 5. Download the fixed Adobe Flash Player version 11.2.202.236 or later for Linux from the official Adobe archive (get.adobe.com/flashplayer)
- 6. Install the new package using the system package manager (e.g., 'yum install flash-plugin-11.2.202.236.x86_64.rpm' or 'zypper install flash-player-11.2.202.236.x86_64.rpm')
- 7. For Adobe AIR, upgrade to version 3.3.0.3610 or later
- 8. Verify the installation was successful by checking the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2039 — 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-2039 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