dbcve.org
AirApplication · Adobe

CVE-2015-8416

HIGH · 10.0 CVSS v2.0 Published 2015-12-10
Fix available
A fix is available. Upgrade to after 19.0.0.241 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
Adobe Flash Player before 18.0.0.268 and 19.x and 20.x before 20.0.0.228 on Windows and OS X and before 11.2.202.554 on Linux, Adobe AIR before 20.0.0.204, Adobe AIR SDK before 20.0.0.204, and Adobe AIR SDK & Compiler before 20.0.0.204 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-8045, CVE-2015-8047, CVE-2015-8060, CVE-2015-8408, CVE-2015-8417, CVE-2015-8418, CVE-2015-8419, CVE-2015-8443, CVE-2015-8444, CVE-2015-8451, and CVE-2015-8455.

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

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors. This is a critical use-after-free or buffer overflow vulnerability in Flash content parsing that received a CVSS score of 10.

MitigationUpgrade Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (Windows/OS X), or 11.2.202.554 (Linux), and Adobe AIR to version 20.0.0.204. If upgrade is not feasible, disable Flash Player in browsers or remove the affected software.

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
AirApplication
Affected:<= 19.0.0.241
Flash PlayerApplication
Affected:<= 11.2.202.548<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245
Air SdkApplication
Affected:<= 19.0.0.241
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.241

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 Adobe Flash Player version in Windows browsers
    Navigate to https://helpx.adobe.com/flash-player.html or type 'about:plugins' in browser address bar to view the Flash Player version, or check C:\Windows\System32\Macromed\Flash for the npapi file version
    Affected if Installed version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  2. Check Adobe Flash Player version on macOS
    Open System Preferences, click Flash Player, and view the Version tab; or check /Library/Internet Plug-Ins/Flash Player.plugin for the version
    Affected if Installed version matches any vulnerable version listed above
  3. Check Adobe AIR runtime version
    Open the AIR application, or on Windows check Add/Remove Programs for Adobe AIR version, or on macOS check /Applications/Adobe AIR for the version
    Affected if Adobe AIR version is 19.0.0.241 or lower
  4. Check Adobe AIR SDK version
    Look for the AIR SDK in the installation directory, or check the version file within the SDK folder (typically includes a version.properties or SDKDescription.xml file)
    Affected if AIR SDK version is 19.0.0.241 or lower

If any installed version of Adobe Flash Player, Adobe AIR, or Adobe AIR SDK matches the affected versions listed in the CVE, the environment is vulnerable to this memory corruption flaw.

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

Upgrade Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (Windows/OS X), or 11.2.202.554 (Linux), and Adobe AIR to version 20.0.0.204. If upgrade is not feasible, disable Flash Player in browsers or remove the affected software.

Recommended fix High confidence

Flash Player: 18.0.0.268+ (Windows/OS X), 20.0.0.228+ (Windows/OS X), or 11.2.202.554+ (Linux); Adobe AIR/SDK: 20.0.0.204+

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting the version check page
  2. 2. Identify the installed Adobe AIR version via 'About Adobe AIR' in the system tray or Help menu
  3. 3. For Flash Player: Download and install the appropriate fixed version from the official Adobe security bulletin (APSB15-32) - version 18.0.0.268+, 20.0.0.228+, or 11.2.202.554+ for Linux
  4. 4. For Adobe AIR: Download and install version 20.0.0.204 or later from adobe.com
  5. 5. For Adobe AIR SDK: Download and install version 20.0.0.204 or later from the Adobe AIR SDK download page
  6. 6. Restart all browsers and verify the updated version numbers after installation
  7. 7. Remove any older, vulnerable Flash Player versions that may remain on the system
Caveat Adobe Flash Player reached end-of-life on December 31, 2020 and is no longer supported; migration to modern alternatives may be required

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

Fix this in Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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