dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2012-2037

HIGH · 9.3 CVSS v2.0 Published 2012-06-09
Fix available
A fix is available. Upgrade to after 11.2.202.235 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
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 or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2012-2034.

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

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. The vulnerability affects multiple versions across Windows, Mac OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to versions 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); update Adobe AIR to version 3.3.0.3610 or later.

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
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 6.2
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server AusOperating system
Affected:= 6.2
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0
Flash PlayerApplication
Affected:<= 11.2.202.235<= 11.1.115.8<= 11.1.111.9
AirApplication
Affected:<= 3.2.0.2070
OpensuseOperating system
Affected:= 11.4= 12.1

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

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

  1. Check Adobe Flash Player version on Windows/Mac
    On Windows, check C:\Windows\System32\Macromed\Flash\ and look at the version info of flash*.ocx or use 'Get-ItemProperty' on the registry key HKLM\SOFTWARE\Macromedia\FlashPlayer. On Mac, check /Library/Application Support/Adobe/Flash Player/ for version files or use 'defaults read' on com.adobe.flashplayer.installpath
    Affected if Version is 11.2.202.235 or lower, 11.1.115.8 or lower, or 11.1.111.9 or lower
  2. Check Adobe Flash Player version on Linux
    Use the package manager (rpm -q flash-plugin or dpkg -l | grep flash) or check /usr/lib/flash-plugin/ for version files
    Affected if Version is 11.2.202.235 or lower
  3. Check Adobe AIR version
    On Windows, check Add/Remove Programs or the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR. On Mac, check /Applications/Adobe AIR Installer.app or use 'ls -la' in /Applications and look for Adobe AIR version info
    Affected if Version is 3.2.0.2070 or lower
  4. Check Red Hat Enterprise Linux version
    Use 'cat /etc/redhat-release' or 'cat /etc/system-release' to identify the RHEL version
    Affected if Version is 5.0, 6.0, or 6.2 (or if the system is listed as Desktop/Server/Workstation Eus/Aus corresponding to 6.2)
  5. Check OpenSUSE version
    Use 'cat /etc/SuSE-release' or 'lsb_release -a' to identify the OpenSUSE version
    Affected if Version is 11.4 or 12.1

You are affected if Adobe Flash Player version falls within the vulnerable ranges (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, OR you run the specific Red Hat Enterprise Linux or OpenSUSE versions listed (5.0, 6.0, 6.2, 11.4, or 12.1) with the affected Adobe software installed.

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.2.202.235
Interim mitigation

Update Adobe Flash Player to versions 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); update Adobe AIR to version 3.3.0.3610 or later.

Recommended fix High confidence

Flash Player 11.2.202.236 or later for Linux; Adobe AIR 3.3.0.3610 or later

  1. 1. Identify the installed Adobe Flash Player version by checking /usr/lib/flash-plugin/ or the browser's plugin information
  2. 2. For Red Hat Enterprise Linux systems: run 'rpm -q flash-plugin' to check the current version
  3. 3. Remove the vulnerable Flash Player package: 'yum remove flash-plugin' or 'rpm -e flash-plugin'
  4. 4. For RHEL 5.x/6.x: Enable the optional and supplementary channels via RHN or Red Hat Satellite
  5. 5. Install the updated package: 'yum install flash-plugin' or 'subscription-manager repos --enable=...' to enable the appropriate channel before installing
  6. 6. Alternatively, download the fixed Flash Player from https://get.adobe.com/flashplayer/ (ensure to select the Linux .rpm or .tar.gz version for your distribution)
  7. 7. For OpenSUSE: Use 'zypper patch' or 'zypper update flash-player' after checking available security patches
  8. 8. Restart all web browsers to ensure the new plugin is loaded
Caveat Flash Player reached end of life for Linux in 2012; consider migrating to HTML5 video alternatives or using a different browser with NPAPI support if possible

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

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2037 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