dbcve.org
Flash PlayerApplication · Adobe

CVE-2010-2170

HIGH · 9.3 CVSS v2.0 Published 2010-06-15
Fix available
A fix is available. Upgrade to after 1.5.3.9130 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Integer overflow in Adobe Flash Player before 9.0.277.0 and 10.x before 10.1.53.64, and Adobe AIR before 2.0.2.12610, might allow attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2010-2181 and CVE-2010-2183.

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
How this class of weakness works · CWE-189

A legacy NVD category grouping numeric mistakes — overflows, truncation, sign errors — where a miscalculated value goes on to drive a dangerous decision such as a memory allocation or a bounds check. It is a bucket rather than one specific bug. Remediation is checked arithmetic and validating any computed size or index before it is used.

General guidance for the numeric errors class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:= 9.0.16= 9.0.20= 9.0.20.0= 9.0.28= 9.0.28.0= 9.0.31= 9.0.31.0= 9.0.45.0= 9.0.47.0= 9.0.48.0= 9.0.115.0= 9.0.124.0
Flash PlayerApplication
Affected:= 5.0= 5.0.30.0= 5.0.41.0= 5.0.42.0= 5.0.58.0
AirApplication
Affected:<= 1.5.3.9130= 1.0= 1.1= 1.5= 1.5.1= 1.5.2= 1.5.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

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 1.5.3.9130
Vendor patch www.adobe.com →
Recommended fix High confidence

Flash Player 9.0.277.0+ (for 9.x branch) or Flash Player 10.1.53.64+ (for 10.x branch); Adobe AIR 2.0.2.12610+

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu or visiting adobe.com/software/flash/about
  2. 2. For Flash Player 9.x users: Download and install Flash Player 9.0.277.0 or later from adobe.com/get/flashplayer
  3. 3. For Flash Player 10.x users: Download and install Flash Player 10.1.53.64 or later from adobe.com/get/flashplayer
  4. 4. For Adobe AIR users: Uninstall current Adobe AIR version, then download and install Adobe AIR 2.0.2.12610 or later from adobe.com/air
  5. 5. Verify installation was successful by checking the version again and confirming it meets the minimum fixed version requirements
  6. 6. Restart any browsers or applications that use Flash Player or Adobe AIR
Caveat Security update may introduce compatibility changes with older Flash content or AIR applications; test critical workflows after upgrade

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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