dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jun 2022.
Flash PlayerApplication · Adobe

CVE-2012-0754

HIGH · 8.1 CVSS v3.1 Published 2012-02-16
Fix available
A fix is available. Upgrade to 10.3.183.15 / 11.1.102.62 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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.15 and 11.x before 11.1.102.62 on Windows, Mac OS X, Linux, and Solaris; before 11.1.111.6 on Android 2.x and 3.x; and before 11.1.115.6 on Android 4.x allows attackers to execute arbitrary code or cause a denial of service (memory corruption) 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 confidence

Memory corruption vulnerability in Adobe Flash Player allowing arbitrary code execution or denial of service. Affects multiple versions across Windows, Mac OS X, Linux, Solaris, and Android platforms. The vulnerability has unspecified attack vectors but leads to memory corruption that can be exploited for code execution.

MitigationUpdate Adobe Flash Player to version 10.3.183.15 or later for 10.x, 11.1.102.62 or later for 11.x on desktop platforms, and corresponding Android versions. Remove Flash Player if unnecessary or deploy via enterprise patch management.

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
Flash PlayerApplication
Affected:< 10.3.183.15>= 11.0, < 11.1.102.62< 11.1.111.6< 11.1.115.6

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Flash Player is installed
    Check for the Flash Player plugin in your browser (visit about:plugins or browser's add-ons) or look for flashocx.dll (Windows), Flash Player.plugin (Mac), or libflashplayer.so (Linux) in system directories
    Affected if Flash Player is present on the system
  2. Identify installed Flash Player version on Windows
    Locate the Flash Player OCX file (flash*.ocx in C:\Windows\System32\Macromed\Flash) or the NPSWF32.dll in browser plugin folders, right-click the file and select Properties > Details to view the File Version
    Affected if The displayed version falls below 10.3.183.15, or is 11.0.x through 11.1.102.61, or (for Android) below 11.1.111.6 (2.x/3.x devices) or below 11.1.115.6 (4.x devices)
  3. Identify installed Flash Player version on Mac OS X
    Locate /Library/Internet Plug-Ins/Flash Player.plugin or ~/Library/Internet Plug-Ins/Flash Player.plugin, right-click the .plugin and select Show Package Contents, then check the Info.plist for CFBundleVersion or CFBundleShortVersionString
    Affected if Version is below 10.3.183.15, or 11.0.x through 11.1.102.61
  4. Identify installed Flash Player version on Linux
    Check /usr/lib/flash-plugin or /usr/lib/adobe-flashplugin for libflashplayer.so, run 'rpm -q flash-plugin' (RHEL/CentOS) or 'dpkg -l flashplugin-installer' (Debian) or inspect the file version with 'file' or a hex editor
    Affected if Version is below 10.3.183.15, or 11.0.x through 11.1.102.61
  5. Identify Flash Player version on Android
    Go to Settings > Applications > Manage Applications on the device, locate Adobe Flash Player, and check the version information under the app details
    Affected if Running Android 2.x/3.x with version below 11.1.111.6, or Android 4.x with version below 11.1.115.6

You are affected if Adobe Flash Player is installed and its version falls into any of these ranges: below 10.3.183.15, 11.0.x through 11.1.102.61, below 11.1.111.6 (Android 2.x/3.x), or below 11.1.115.6 (Android 4.x).

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 10.3.183.15 / 11.1.102.62 / 11.1.111.6 or later
Fixed in 10.3.183.1511.1.102.6211.1.111.6
Vendor patch www.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 10.3.183.15 or later for 10.x, 11.1.102.62 or later for 11.x on desktop platforms, and corresponding Android versions. Remove Flash Player if unnecessary or deploy via enterprise patch management.

Recommended fix High confidence

Flash Player 10.3.183.15 (or 11.1.102.62 for 11.x) – choose the appropriate version for your platform

  1. Check the currently installed Flash Player version (e.g., in Chrome open chrome://plugins, in Firefox go to Add‑ons > Plugins, or on Android go to Settings > Applications > Adobe Flash Player).
  2. Identify the correct fixed version for your platform: for Windows, macOS, Linux, or Solaris upgrade to 10.3.183.15 or 11.1.102.62; for Android 2.x/3.x upgrade to 11.1.111.6; for Android 4.x upgrade to 11.1.115.6.
  3. Open the Adobe security bulletin APSB12‑03 (https://www.adobe.com/support/security/bulletins/apsb12-03.html) and download the installer that matches your OS and architecture.
  4. Run the installer and follow the on‑screen prompts to apply the update.
  5. Restart the web browser (or reboot the device on Android).
  6. Verify the installed Flash Player version matches the fixed release (e.g., check the plugin page again) to confirm the update succeeded.
Caveat No major breaking changes reported; some legacy plugins may become unsupported after the upgrade

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

Fix this in Flash Player Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0754 — 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-0754 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