CVE-2010-2216
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 · uneditedAdobe 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-2214.
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 confidenceMemory 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.
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 dataall versions= 1.0= 1.0.1= 1.5= 1.5.1= 1.5.3= 1.5.3.9120all 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= 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.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Adobe Flash Player version on WindowsOpen the Flash Player Settings Manager at https://www.adobe.com/support/flashplayer/settings.html, or check the version via the Windows registry at HKLM\SOFTWARE\Macromedia\FlashPlayer\VersionAffected if The installed version is 10.1.53.64 or earlier, or is 9.x before 9.0.280, or is any 7.x or 8.x version listed in the affected versions, or is a 10.x version before 10.1.82.76
-
Check Adobe Flash Player version on LinuxRun the command 'rpm -q flash-plugin' for RPM-based systems, or check the library file version at /usr/lib/flash-plugin/libflashplayer.so using 'file' or checking the package detailsAffected if The installed version is 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, or any version before 9.0.280 (for 9.x) or before 10.1.82.76 (for 10.x)
-
Check Adobe AIR versionRun 'airappinstaller -version' from the command line, or check the version in the Adobe AIR application info typically found in the installation directory or via the application's propertiesAffected if The installed version is 1.0, 1.0.1, 1.5, 1.5.1, 1.5.3, or 1.5.3.9120 (any version before 2.0.3)
The environment is affected if Adobe Flash Player is any version before 9.0.280 (9.x), any version before 10.1.82.76 (10.x), or any of the specific 7.x or 8.x versions listed; or if Adobe AIR is any version before 2.0.3.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Adobe Flash Player to version 9.0.280 or later (10.x to 10.1.82.76 or later) and Adobe AIR to version 2.0.3 or later to remediate this vulnerability.
Adobe Flash Player 9.0.280+ (9.x) or 10.1.82.76+ (10.x); Adobe AIR 2.0.3+
- Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or checking the system's package manager
- Identify the installed Adobe AIR version by checking the application's properties or version information
- For Adobe Flash Player 9.x line: upgrade to version 9.0.280 or later
- For Adobe Flash Player 10.x line: upgrade to version 10.1.82.76 or later
- For Adobe AIR: upgrade to version 2.0.3 or later
- Verify the upgrade was successful by checking the new version numbers
- Restart any browsers or applications using the affected software
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2216 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-2216 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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