dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8415

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
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.

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 affecting multiple versions (prior to 18.0.0.268/20.0.0.228 for Flash, prior to 20.0.0.204 for AIR) on Windows, OS X, and Linux. Allows remote attackers to execute arbitrary code via unspecified vectors.

MitigationUpdate Adobe Flash Player to version 18.0.0.268 or later (20.0.0.228 for versions 19.x/20.x) and Adobe AIR to version 20.0.0.204 or later across all affected endpoints.

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:<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245<= 11.2.202.548
AirApplication
Affected:<= 19.0.0.241
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 on Windows
    Open Windows Control Panel, go to Programs and Features, find Adobe Flash Player in the list, and note the version number displayed
    Affected if The version is 18.0.0.261 or lower, any of 19.0.0.185/207/226/245, or 11.2.202.548 or lower
  2. Check Adobe Flash Player version on Mac OS X
    Open System Preferences, click on Flash Player, then go to the Storage tab to view the version number
    Affected if The version is 18.0.0.261 or lower, any of 19.0.0.185/207/226/245, or 11.2.202.548 or lower
  3. Check Adobe Flash Player version on Linux
    Navigate to /usr/lib/flash-plugin/ and run the command: ./flash-player-properties or check the version via package manager (dpkg -l | grep flash or rpm -q flash-plugin)
    Affected if The version is 18.0.0.261 or lower, any of 19.0.0.185/207/226/245, or 11.2.202.548 or lower
  4. Check Adobe AIR version
    Open the Adobe AIR application on the system, navigate to Help > About Adobe AIR, or check the installed version via the system add/remove programs utility
    Affected if The version is 19.0.0.241 or lower (note: fixed version is 20.0.0.204)
  5. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory and open the README or version file, or run: adt -version from the AIR SDK bin directory
    Affected if The SDK version is 19.0.0.241 or lower

Your environment is affected if any installed Adobe Flash Player or Adobe AIR/AIR SDK version matches the affected ranges listed in the CVE, particularly versions 19.0.0.245 and below, or 18.0.0.261 and below.

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 later (20.0.0.228 for versions 19.x/20.x) and Adobe AIR to version 20.0.0.204 or later across all affected endpoints.

Recommended fix High confidence

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

  1. Identify the installed Adobe Flash Player version by navigating to About Flash Player in the browser
  2. Identify the installed Adobe AIR version in Control Panel (Windows) or System Preferences (Mac)
  3. Download the fixed Flash Player version 20.0.0.228 or later from adobe.com
  4. Download the fixed Adobe AIR version 20.0.0.204 or later from adobe.com
  5. Download the fixed Adobe AIR SDK version 20.0.0.204 or later from adobe.com if using the SDK
  6. Uninstall all existing Flash Player installations
  7. Install the updated Flash Player 20.0.0.228 or later
  8. Install the updated Adobe AIR 20.0.0.204 or later
Caveat Flash Player is deprecated and no longer supported; consider removing it entirely if functionality is not required

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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-2015-8415 — 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-8415 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