dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022.
Flash PlayerApplication · Adobe

CVE-2016-1010

HIGH · 8.8 CVSS v3.1 Published 2016-03-12
Fix available
A fix is available. Upgrade to after 20.2.2.306 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges 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 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows and OS X and before 11.2.202.577 on Linux, Adobe AIR before 21.0.0.176, Adobe AIR SDK before 21.0.0.176, and Adobe AIR SDK & Compiler before 21.0.0.176 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2016-0963 and CVE-2016-0993.

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

Integer overflow vulnerability in Adobe Flash Player and Adobe AIR that allows remote attackers to execute arbitrary code via unspecified vectors. The overflow occurs in memory allocation handling, enabling code execution when the calculated size exceeds expected bounds.

MitigationUpdate Adobe Flash Player to version 18.0.0.333, 21.0.0.182 or later (or 11.2.202.577+ for Linux); update Adobe AIR to 21.0.0.176 or later. Given Flash's end-of-life status, consider removal if业务 requirements permit.

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
Flash PlayerApplication
Affected:<= 20.0.0.306<= 11.2.202.569
AirApplication
Affected:<= 20.0.0.233
Air SdkApplication
Affected:<= 20.0.0.260
X14j FirmwareOperating system
Affected:= t-ms14jakucb-1102.5
Flash Player Desktop RuntimeApplication
Affected:<= 20.2.2.306
Air Desktop RuntimeApplication
Affected:<= 20.0.0.260
Air Sdk \& CompilerApplication
Affected:<= 20.0.0.260

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 on Windows or macOS browsers
    Navigate to the Adobe Flash Player version page in a web browser (go to https://helpx.adobe.com/flash-player.html or type 'about:plugin' in URL bar for some browsers), or check the file version of npapi32.dll (typically in C:\Windows\System32\Macromed\Flash\ on Windows or /Library/Internet Plug-Ins/Flash Player.plugin on macOS)
    Affected if The installed version is less than 18.0.0.333 for 18.x branch, or less than 21.0.0.182 for 19.x-21.x branches, or less than 11.2.202.577 on Linux, or falls within the ranges <= 20.0.0.306, <= 11.2.202.569, or <= 20.2.2.306 for Desktop Runtime
  2. Check Adobe Flash Player version on Linux
    Locate the libflashplayer.so file (typically in /usr/lib/flash-plugin/ or /usr/lib/mozilla/plugins/) and run: ls -la or rpm -q flash-plugin, or check the file version property of libflashplayer.so
    Affected if The version is less than 11.2.202.577 or matches <= 11.2.202.569 from the affected products list
  3. Check Adobe AIR Desktop Runtime version on Windows
    Open Windows Control Panel > Programs and Features, or check the file version of AIR.dll in the Adobe AIR installation directory (typically C:\Program Files\Adobe\Adobe AIR\ or C:\Program Files (x86)\Adobe\Adobe AIR\)
    Affected if The version is less than 21.0.0.176 or falls within <= 20.0.0.233 or <= 20.0.0.260 (Desktop Runtime)
  4. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory and check the version file (version.xml or similar), or run: adt -version if the SDK compiler is installed, or examine the AIR SDK download file name
    Affected if The SDK version is <= 20.0.0.260 (Adobe Air Sdk or Adobe Air Sdk & Compiler)
  5. Check Samsung X14j laptop firmware version
    Access the laptop BIOS/UEFI firmware settings on boot (typically press F2 or Del), or use system information tools like wmic bios get version or dmidecode on Linux, looking for firmware version string
    Affected if The firmware version string equals t-ms14jakucb-1102.5 exactly

You are affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches or falls below the affected version ranges for your platform, or if a Samsung X14j laptop has firmware version t-ms14jakucb-1102.5.

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 20.2.2.306
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 18.0.0.333, 21.0.0.182 or later (or 11.2.202.577+ for Linux); update Adobe AIR to 21.0.0.176 or later. Given Flash's end-of-life status, consider removal if业务 requirements permit.

Recommended fix High confidence

Flash Player 21.0.0.182 (Windows/OS X), 11.2.202.577 (Linux); Adobe AIR/SDK 21.0.0.176

  1. 1. Verify current Adobe Flash Player version by navigating to https://www.adobe.com/software/flash/about/ in a browser
  2. 2. For Windows/OS X: Download Flash Player 21.0.0.182 from the official Adobe Flash Player download page (https://get.adobe.com/flashplayer/)
  3. 3. For Linux: Download Flash Player 11.2.202.577 from the official Adobe archives or Linux distribution package manager
  4. 4. For Adobe AIR users: Download AIR 21.0.0.176 from the official Adobe AIR download page
  5. 5. For developers using AIR SDK: Download AIR SDK 21.0.0.176 from the Adobe AIR SDK download page
  6. 6. Close all browsers and applications that use Flash Player
  7. 7. Run the installer with administrative privileges
  8. 8. Restart browsers after installation completes
Caveat Minimal risk - this is a security patch upgrade; verify critical Flash-based applications still function properly after update

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

Fix this in Flash Player Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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