dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8407

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
Stack-based buffer overflow in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-8457.

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

Stack-based buffer overflow in Adobe Flash Player and AIR allows arbitrary code execution via unspecified vectors. The vulnerability enables attackers to overflow a stack-allocated buffer, potentially overwriting return addresses and achieving code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.268 or 20.0.0.228 (or later), and Adobe AIR to 20.0.0.204 or later. Given Flash Player end-of-life status, consider removing it entirely if possible.

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:<= 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
AirApplication
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 for installed Adobe Flash Player version
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion (32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\CurrentVersion (64-bit). Alternatively, locate the Flash Player plugin file ( NPSWF32.dll or Flash32_*.ocx in the browser plugins folder) and view its file properties. On macOS, check /Library/Internet Plug-Ins/Flash Player.plugin and use 'Get Info' to view version.
    Affected if The 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 for installed Adobe AIR version
    On Windows, open Programs and Features (or Add/Remove Programs) and look for 'Adobe AIR' in the installed programs list to see the version number. On macOS, check /Applications/Adobe AIR Installer.app and view its version via 'Get Info', or run 'system_profiler SPApplicationsDataType' in Terminal.
    Affected if The installed version is 19.0.0.241 or earlier
  3. Check for Adobe AIR SDK installation
    On Windows, look in the installation directory (commonly C:\Program Files\Adobe\Adobe AIR SDK or C:\Users\Username\AppData\Local\Adobe\AIR) for the AIR SDK version file or the SDK's readme/version text file. On macOS, check /Library/Application Support/Adobe/AIR or the user-specific AIR SDK folder.
    Affected if The installed Adobe AIR SDK version is 19.0.0.241 or earlier
  4. Verify browser plugin status
    Open each installed web browser, navigate to its Add-ons or Extensions manager, and locate the Adobe Flash Player plugin section. Note whether the plugin is enabled or disabled. For Chrome, type 'chrome://plugins' in the address bar.
    Affected if Adobe Flash Player plugin is present and enabled in any browser, and the version matches the affected ranges listed above

If Adobe Flash Player or AIR is installed and its version falls within 11.2.202.548 or lower, 18.0.0.261 or lower, or any of the specific 19.0.x versions (185, 207, 226, 245), or AIR SDK 19.0.0.241 or lower, the environment is vulnerable to this CVE.

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

Update Adobe Flash Player to version 18.0.0.268 or 20.0.0.228 (or later), and Adobe AIR to 20.0.0.204 or later. Given Flash Player end-of-life status, consider removing it entirely if possible.

Recommended fix High confidence

Flash Player 20.0.0.228 (Windows/OS X), Flash Player 11.2.202.554 (Linux), Adobe AIR 20.0.0.204, Adobe AIR SDK 20.0.0.204

  1. Identify the currently installed Adobe Flash Player version via https://helpx.adobe.com/flash-player.html
  2. For Windows or OS X: Upgrade Flash Player to version 20.0.0.228 or later from adobe.com/get/flashplayer
  3. For Linux: Upgrade Flash Player to version 11.2.202.554 or later from adobe.com/get/flashplayer
  4. For Adobe AIR (desktop runtime): Upgrade to version 20.0.0.204 or later
  5. For Adobe AIR SDK: Upgrade to version 20.0.0.204 or later
  6. For Adobe AIR SDK & Compiler: Upgrade to version 20.0.0.204 or later
  7. Verify the updated version number after installation

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

Fix this in Flash Player 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-8407 — 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-8407 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