dbcve.org
ChromeWeb browser · Google

CVE-2012-0724

HIGH · 9.3 CVSS v2.0 Published 2012-04-06
Fix available
A fix is available. Upgrade to 3.2.0.2070 / 11.1.111.8 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 11.2.202.229 in Google Chrome before 18.0.1025.151 allow attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2012-0725.

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 · moderate confidence

Memory corruption vulnerability in Adobe Flash Player before 11.2.202.229 (bundled with Google Chrome before 18.0.1025.151) allows attackers to cause denial of service or potentially achieve unspecified code execution via unknown vectors.

MitigationUpdate Adobe Flash Player to version 11.2.202.229 or later, and update Google Chrome to version 18.0.1025.151 or later. Note: Adobe Flash Player reached end-of-life in December 2020 and should be removed entirely from modern systems.

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
ChromeWeb browser
Affected:< 18.0.1025.151
Flash PlayerApplication
Affected:< 11.2.202.229< 11.2.202.228< 11.2.202.223< 11.1.111.8
AirApplication
Affected:< 3.2.0.2070

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. Identify installed Adobe Flash Player version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Adobe Flash Player Plug-In}, or check the file version of NPSWF32.dll in the Windows\System32\Macromed\Flash folder
    Affected if The installed version is less than 11.2.202.229, or falls between 11.2.202.228 and 11.2.202.223, or is less than 11.1.111.8
  2. Identify installed Adobe Air version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Air, or check the version of the Adobe Air installer or runtime folder
    Affected if The installed version is less than 3.2.0.2070
  3. Identify Google Chrome version
    Open Chrome, click the menu icon, select Help, then About Google Chrome, or run 'chrome --version' from command line
    Affected if The Chrome version is less than 18.0.1025.151 (which bundles a vulnerable Flash Player)
  4. Identify bundled Flash Player version within Chrome
    In Chrome address bar, enter chrome://plugins, locate the Flash entry, and check the version shown
    Affected if The bundled Flash version within Chrome is less than 11.2.202.229

You are affected if Adobe Flash Player is installed at any version below 11.2.202.229, Adobe Air is below 3.2.0.2070, or Google Chrome is below version 18.0.1025.151 with its bundled Flash.

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 3.2.0.2070 / 11.1.111.8 / 11.2.202.223 or later
Fixed in 3.2.0.207011.1.111.811.2.202.223
Interim mitigation

Update Adobe Flash Player to version 11.2.202.229 or later, and update Google Chrome to version 18.0.1025.151 or later. Note: Adobe Flash Player reached end-of-life in December 2020 and should be removed entirely from modern systems.

Recommended fix High confidence

Chrome 18.0.1025.151+ | Flash Player 11.2.202.229+ | Adobe AIR 3.2.0.2070+

  1. 1. Identify which Adobe products are installed: check for Adobe Flash Player, Adobe AIR, and Google Chrome with bundled Flash.
  2. 2. For Google Chrome users: Upgrade Chrome to version 18.0.1025.151 or later. Chrome auto-updates, but manual update can be triggered via Chrome menu > Help > About Google Chrome.
  3. 3. For Adobe Flash Player standalone: Download and install Flash Player 11.2.202.229 or later from the official Adobe website (get.adobe.com/flashplayer).
  4. 4. For Adobe AIR: Upgrade to version 3.2.0.2070 or later from the official Adobe AIR download page.
  5. 5. Verify the installed versions after upgrade: Check Flash version at about:plugins in Chrome, or through Adobe's version check page.
  6. 6. Restart all browsers and applications after applying updates.
Caveat This is a 2012 vulnerability; upgrading to these older fixed versions may require accepting older software versions. Consider upgrading to more current stable releases if compatible with your system requirements.

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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