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

MEDIUM · 6.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 Remotely reachable No privileges 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
Cross-site scripting (XSS) vulnerability in 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 remote attackers to inject arbitrary web script or HTML via unspecified vectors, aka "Universal XSS (UXSS)," as exploited in the wild in February 2012.

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

A Universal Cross-Site Scripting (UXSS) vulnerability in Adobe Flash Player allows remote attackers to inject arbitrary web script or HTML through unspecified vectors. The flaw affects multiple versions across Windows, Mac OS X, Linux, Solaris, and Android platforms. This was actively exploited in the wild in February 2012.

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 systems, 11.1.111.6 or later for Android 2.x/3.x, and 11.1.115.6 or later for Android 4.x. Consider removing Flash Player entirely as it is deprecated and no longer supported.

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Verify Adobe Flash Player is installed
    Windows: Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion or look for flashplayer*.exe in system directories. Mac: Check /Library/Application Support/Adobe/Flash Player/ for installed components. Linux: Run 'rpm -q flash-player' or check /usr/lib/flash-plugin/
    Affected if Adobe Flash Player is present on the system
  2. Identify the installed Flash Player version number
    Windows: Right-click the Flash Player DLL or check About Flash in browser. Mac: Run 'defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion' in Terminal. Linux: Run 'rpm -q --queryformat "%{VERSION}" flash-player'
    Affected if The version cannot be determined or is older than the ranges listed
  3. Compare your version against affected ranges
    Match your installed version to these vulnerable ranges: < 10.3.183.15, OR >= 11.0 and < 11.1.102.62, OR < 11.1.111.6 (for 11.1.x), OR < 11.1.115.6 (for 11.1.x on Android). The specific range depends on whether you are on the 10.x or 11.x branch.
    Affected if Your installed version falls into any of these ranges: less than 10.3.183.15, 11.0 to below 11.1.102.62, below 11.1.111.6, or below 11.1.115.6
  4. Confirm Flash Player plugin is enabled in browsers
    Check browser add-on or plugin settings. In Internet Explorer, go to Manage Add-ons. In Firefox, go to Add-ons > Plugins. In Chrome, go to chrome://plugins. Verify the Flash Player plugin is set to 'Always Activate' or enabled.
    Affected if The Flash Player plugin is enabled and active in any web browser on the system

You are affected if Adobe Flash Player is installed with a version matching any of the vulnerable ranges and the Flash plugin is enabled in a web browser, as the UXSS flaw requires active Flash content rendering in pages.

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 systems, 11.1.111.6 or later for Android 2.x/3.x, and 11.1.115.6 or later for Android 4.x. Consider removing Flash Player entirely as it is deprecated and no longer supported.

Recommended fix High confidence

Flash Player 10.3.183.15 / 11.1.102.62 (desktop); 11.1.111.6 (Android 2.x/3.x); 11.1.115.6 (Android 4.x)

  1. Identify the current Adobe Flash Player version installed on affected systems
  2. For Windows, Mac OS X, Linux, and Solaris: Upgrade to version 10.3.183.15 or later, or 11.1.102.62 or later
  3. For Android 2.x and 3.x devices: Upgrade to version 11.1.111.6 or later
  4. For Android 4.x devices: Upgrade to version 11.1.115.6 or later
  5. Verify the upgrade was successful by checking the Flash Player version in the About section
  6. Note: Adobe Flash Player reached end of life on December 31, 2020 - consider migrating away from Flash-based content
Caveat Flash Player reached end of life on December 31, 2020 and is no longer supported; modern browsers have disabled Flash by default

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

Fix this in Flash Player Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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-0767 — 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-0767 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