Flash PlayerApplication · Adobe

CVE-2015-6678

HIGH · 10.0 CVSS v2.0 Published 2015-09-22
Fix available
A fix is available. Upgrade to after 18.0.0.199 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
Buffer overflow in Adobe Flash Player before 18.0.0.241 and 19.x before 19.0.0.185 on Windows and OS X and before 11.2.202.521 on Linux, Adobe AIR before 19.0.0.190, Adobe AIR SDK before 19.0.0.190, and Adobe AIR SDK & Compiler before 19.0.0.190 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-6676.

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

Buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. Affects specific versions across Windows, OS X, and Linux platforms, as well as AIR SDK and AIR SDK & Compiler.

MitigationUpdate Adobe Flash Player to version 18.0.0.241+/19.0.0.185+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR to 19.0.0.190+. Remove if no longer needed.

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:<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246= 16.0.0.235
AirApplication
Affected:<= 18.0.0.199<= 18.0.0.143
Air SdkApplication
Affected:<= 18.0.0.199
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.180
AndroidOperating system
Affected:all versions

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 on Windows
    Inspect the version property of the Flash Player DLL at C:\Windows\System32\Macromed\Flash\Flash*.ocx, or query the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion
    Affected if The installed version is 13.0.0.289 or earlier; equals 14.0.0.125, 14.0.0.145, 14.0.0.176, or 14.0.0.179; equals 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, or 15.0.0.246; or equals 16.0.0.235
  2. Check Adobe Flash Player version on macOS
    Inspect the version file or Info.plist in /Library/Application Support/Adobe/Flash Player/ and within each installed browser plugin directory such as /Library/Internet Plug-Ins/
    Affected if The installed version is 13.0.0.289 or earlier; equals 14.0.0.125, 14.0.0.145, 14.0.0.176, or 14.0.0.179; equals 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, or 15.0.0.246; or equals 16.0.0.235
  3. Check Adobe Flash Player version on Linux
    Examine the version file typically found in /usr/lib/flash-plugin/ or /opt/flashplugin-installer/, or run 'rpm -q flash-plugin' or 'dpkg -l flashplugin-installer'
    Affected if The installed version is 13.0.0.289 or earlier; equals 14.0.0.125, 14.0.0.145, 14.0.0.176, or 14.0.0.179; equals 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, or 15.0.0.246; or equals 16.0.0.235
  4. Check Adobe AIR runtime version
    View the version information for the Adobe AIR application installer at C:\Program Files (x86)\Adobe\AIR\ on Windows or /Applications/Adobe AIR Application Installer.app on macOS, or check the AIR runtime DLL at C:\Users\%USERNAME%\AppData\Local\Adobe\AIR\
    Affected if The installed version is 18.0.0.199 or earlier, or 18.0.0.143 or earlier
  5. Check Adobe AIR SDK version
    Inspect the version file within the installed AIR SDK directory, commonly found in the SDK's bin or flex-sdk directories, or check the AIR SDK & Compiler installation folder
    Affected if The AIR SDK version is 18.0.0.199 or earlier, or the AIR SDK & Compiler version is 18.0.0.180 or earlier
  6. Check for Flash Player on Android devices
    On Android, verify the Flash Player APK is installed by checking the system settings under Apps or using an app like Package Manager to list installed packages containing 'flash'
    Affected if Adobe Flash Player for Android is installed on any version of Google Android

A user is affected if any installed Adobe Flash Player, Adobe AIR, AIR SDK, or AIR SDK & Compiler version matches one of the vulnerable versions listed, or if Flash Player is present on any Android device.

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

Update Adobe Flash Player to version 18.0.0.241+/19.0.0.185+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR to 19.0.0.190+. Remove if no longer needed.

Recommended fix High confidence

Flash Player 18.0.0.241+/19.0.0.185+ (Windows/OS X), 11.2.202.521+ (Linux); Adobe AIR 19.0.0.190+; Adobe AIR SDK 19.0.0.190+

  1. Identify the exact installed Adobe Flash Player version (check Help > About Adobe Flash Player)
  2. Identify the exact installed Adobe AIR version (check Help > About Adobe Adobe AIR)
  3. Download Adobe Flash Player version 18.0.0.241 or later (or 19.0.0.185 or later for the 19.x branch) from the official Adobe website
  4. For Linux systems, download version 11.2.202.521 or later
  5. For Adobe AIR, download version 19.0.0.190 or later from the Adobe AIR download page
  6. For Adobe AIR SDK, download version 19.0.0.190 or later from the Adobe AIR SDK download page
  7. Close all browser instances that may be running Flash content
  8. Install the Adobe Flash Player update and restart browsers
Caveat Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content entirely as no further updates will be available

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6678 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