dbcve.org
ChromeWeb browser · Google

CVE-2012-0725

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-0724.

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 before 11.2.202.229 (in Google Chrome before 18.0.1025.151) allows attackers to cause denial of service or possibly achieve unspecified other impact 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 to remediate this vulnerability.

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. Check Adobe Flash Player version in Windows
    Open Control Panel > Programs and Features, or navigate to C:\Windows\System32\Macromed\Flash\ and locate the Flash*.ocx file. Right-click the file, select Properties, and view the Version tab.
    Affected if The displayed version is earlier than 11.2.202.223, or falls between 11.2.202.223 and 11.2.202.228 (inclusive), or is earlier than 11.1.111.8, or is any version before 11.2.202.229.
  2. Check Adobe Flash Player version in browsers
    In Google Chrome, navigate to chrome://plugins, find the Flash plugin, and note the version. In Mozilla Firefox, go to Add-ons > Plugins and locate the Shockwave Flash entry.
    Affected if The Flash plugin version shown is earlier than 11.2.202.229, or matches any of the affected version ranges (< 11.2.202.228, < 11.2.202.223, or < 11.1.111.8).
  3. Check Google Chrome version
    Launch Google Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number is displayed on that page.
    Affected if The Chrome version is earlier than 18.0.1025.151.
  4. Check Adobe Air version
    Open Control Panel > Programs and Features (or Add or Remove Programs on older Windows), locate Adobe Air in the list, and note the version shown.
    Affected if The Adobe Air version is earlier than 3.2.0.2070.

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

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 to remediate this vulnerability.

Recommended fix High confidence

Chrome 18.0.1025.151 | Flash Player 11.2.202.229 | Air 3.2.0.2070

  1. Identify which affected product is in use: Google Chrome, Adobe Flash Player, or Adobe Air
  2. If using Google Chrome: Upgrade to version 18.0.1025.151 or later
  3. If using Adobe Flash Player: Upgrade to version 11.2.202.229 or later (or the latest 11.x version available)
  4. If using Adobe Air: Upgrade to version 3.2.0.2070 or later
  5. After upgrading, verify the installed version matches or exceeds the fixed release

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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