dbcve.org
Adobe AirApplication · Adobe

CVE-2010-2214

HIGH · 9.3 CVSS v2.0 Published 2010-08-11
Fix available
A fix is available. Upgrade to after 10.1.53.64 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 9.0.280 and 10.x before 10.1.82.76, and Adobe AIR before 2.0.3, allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2010-0209, CVE-2010-2213, and CVE-2010-2216.

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 (versions before 9.0.280 and 10.x before 10.1.82.76) and Adobe AIR (before 2.0.3) allows remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. The vulnerability stems from improper memory handling that can be exploited to achieve code execution or crash the application.

MitigationUpgrade Adobe Flash Player to version 9.0.280 or 10.1.82.76+, and Adobe AIR to 2.0.3+. For legacy systems where Flash cannot be updated, migrate away from Flash-based content as Flash has reached end-of-life and no longer receives security updates.

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
Adobe AirApplication
Affected:all versions= 1.0= 1.0.1= 1.5= 1.5.1= 1.5.3= 1.5.3.9120
Flash PlayerApplication
Affected:all versions<= 10.1.53.64= 7.0= 7.0.1= 7.0.25= 7.0.63= 7.1.1= 7.2= 8.0= 8.0.22.0= 8.0.33.0= 8.0.34.0
Flash Player For LinuxApplication
Affected:= 9.0.31= 9.0.48.0= 9.0.115.0= 9.0.124.0= 9.0.151.0= 10.0.12.36= 10.0.15.3

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 Flash Player version on Windows
    Open a web browser and visit a Flash version detection page (such as the Adobe Flash Player Help page or type 'about:plugins' in Firefox to list installed plugins). Alternatively, check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer for the version value.
    Affected if The reported version is lower than 9.0.280 (for 9.x branches) or lower than 10.1.82.76 (for 10.x branches), or matches any of the specific affected versions listed (7.0, 7.0.1, 7.0.25, 7.0.63, 7.1.1, 7.2, 8.0, 8.0.22.0, 8.0.33.0, 8.0.34.0, 10.0.12.36, 10.0.15.3, or 10.1.53.64).
  2. Check Flash Player version on Linux
    Open a terminal and run the command 'rpm -q flash-plugin' for RPM-based distributions, or check the browser plugin directory (typically /usr/lib/flash-plugin/ or ~/.mozilla/plugins/) for the Flash library file. Use 'dpkg -l | grep flash' on Debian-based systems.
    Affected if The installed version matches 9.0.31, 9.0.48.0, 9.0.115.0, 9.0.124.0, 9.0.151.0, 10.0.12.36, or 10.0.15.3.
  3. Check Adobe AIR version on Windows
    Open Windows Control Panel and view the list of installed programs, or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR for the Version value. The version can also be found in the Adobe AIR application folder.
    Affected if The installed version is any version before 2.0.3, including 1.0, 1.0.1, 1.5, 1.5.1, 1.5.3, or 1.5.3.9120.
  4. Check Adobe AIR version on Mac
    Open Finder, navigate to the /Library/Application Support/Adobe/AIR folder, or view the application in the Applications folder and select Get Info to see the version number.
    Affected if The installed version is any version before 2.0.3.

You are affected if Flash Player version is below 9.0.280 (for 9.x) or below 10.1.82.76 (for 10.x), or if Adobe AIR version is below 2.0.3.

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 10.1.53.64
Interim mitigation

Upgrade Adobe Flash Player to version 9.0.280 or 10.1.82.76+, and Adobe AIR to 2.0.3+. For legacy systems where Flash cannot be updated, migrate away from Flash-based content as Flash has reached end-of-life and no longer receives security updates.

Recommended fix High confidence

Flash Player 9.0.280+ (9.x) or 10.1.82.76+ (10.x); Adobe AIR 2.0.3+

  1. Identify the currently installed Adobe Flash Player version by navigating to the Adobe Flash Player About page or checking the version in your system's installed programs.
  2. For Adobe Flash Player 9.x users: Upgrade to version 9.0.280 or later.
  3. For Adobe Flash Player 10.x users: Upgrade to version 10.1.82.76 or later.
  4. For Adobe AIR users: Upgrade to version 2.0.3 or later.
  5. Download the updates from the official Adobe Security Bulletins page (APSB10-16) or the Adobe Flash Player download page.
  6. Install the updated version and restart any affected browsers or applications.
  7. Verify the installed version matches or exceeds the fixed release versions specified.
Caveat Upgrading Flash Player or AIR may affect compatibility with older content or applications that rely on specific plugin versions; test in a non-production environment first if possible

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

Fix this in Adobe Air Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
24.0 hours of engineering $4,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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