CVE-2010-0209
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-2213, CVE-2010-2214, 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 · 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 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 for Adobe Flash Player installationWindows: Look for 'C:\Windows\System32\Macromed\Flash\FlashPlayerInstaller.exe' or check Add/Remove Programs. Mac: Check /Library/Internet Plug-Ins/ for 'Flash Player.plugin'. Linux: Check /usr/lib/flash-plugin/ or /opt/flash-player/ directories.Affected if Flash Player is present on the system
-
Determine installed Flash Player versionWindows: Right-click on a Flash content in browser and select 'About Adobe Flash Player', or check the file version of 'C:\Windows\System32\Macromed\Flash\Flash10t.ocx' (or Flash9.ocx for version 9). Mac: Right-click Flash content and select 'About Adobe Flash Player'. Linux: Run 'rpm -q flash-plugin' or 'dpkg -l | grep flash' or check the plugin file properties.Affected if Version is 9.0.x below 9.0.280, or 10.x at or below 10.1.53.64, or any 7.x/8.x version listed in affected versions, or version 10.0.12.36 or 10.0.15.3 on Linux
-
Check Adobe AIR installation statusWindows: Look in 'C:\Program Files\Adobe\Adobe AIR\' directory or check Add/Remove Programs for 'Adobe AIR'. Mac: Check /Applications/ for Adobe AIR application. Linux: Check /opt/adobe-air/ or run 'rpm -q adobe-air' or 'dpkg -l | grep adobe-air'.Affected if Adobe AIR is installed on the system
-
Determine installed Adobe AIR versionWindows: Check the file version of 'Adobe AIR Application Installer.exe' in the Adobe AIR folder, or view properties of the installed Adobe AIR in Add/Remove Programs. Mac: Right-click Adobe AIR in Applications and select 'Get Info'. Linux: Run 'rpm -q adobe-air' or check version file in the installation directory.Affected if 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)
-
Verify browser plugin version (if Flash used in browsers)In Firefox: Type 'about:plugins' in address bar and locate Shockwave Flash entry. In Internet Explorer: Go to 'Manage Add-ons' and check for Flash Player ActiveX version. In Chrome: Type 'chrome://plugins' and locate Flash entry.Affected if Browser plugin version matches the vulnerable Flash Player version ranges above
A system is affected if Adobe Flash Player version is below 9.0.280 (for 9.x), below 10.1.82.76 (for 10.x), or is any 7.x/8.x version, or if Adobe AIR version is below 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 · scopedUpdate Adobe Flash Player to version 9.0.280+, 10.1.82.76+, or later, and Adobe AIR to version 2.0.3 or later to remediate the memory corruption vulnerability.
- This CVE applies to Adobe Flash Player and Adobe AIR, which are END-OF-LIFE products. Adobe Flash Player was officially deprecated on December 31, 2020 and no longer receives security updates.
- Do not attempt to upgrade to a newer version of Flash Player or AIR as they are no longer supported.
- Identify any systems still running Flash Player or Adobe AIR and remove these applications entirely.
- If Flash content is required, use HTML5 alternatives or authorized commercial solutions that still support Flash content (such as Adobe Animate for content creation).
- For legacy internal applications that require Flash, plan to migrate to modern web technologies.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0209 — 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-0209 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