dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8411

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
Public exploit 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
Use-after-free vulnerability 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-8048, CVE-2015-8049, CVE-2015-8050, CVE-2015-8055, CVE-2015-8056, CVE-2015-8057, CVE-2015-8058, CVE-2015-8059, CVE-2015-8061, CVE-2015-8062, CVE-2015-8063, CVE-2015-8064, CVE-2015-8065, CVE-2015-8066, CVE-2015-8067, CVE-2015-8068, CVE-2015-8069, CVE-2015-8070, CVE-2015-8071, CVE-2015-8401, CVE-2015-8402, CVE-2015-8403, CVE-2015-8404, CVE-2015-8405, CVE-2015-8406, CVE-2015-8410, CVE-2015-8412, CVE-2015-8413, CVE-2015-8414, CVE-2015-8420, CVE-2015-8421, CVE-2015-8422, CVE-2015-8423, CVE-2015-8424, CVE-2015-8425, CVE-2015-8426, CVE-2015-8427, CVE-2015-8428, CVE-2015-8429, CVE-2015-8430, CVE-2015-8431, CVE-2015-8432, CVE-2015-8433, CVE-2015-8434, CVE-2015-8435, CVE-2015-8436, CVE-2015-8437, CVE-2015-8441, CVE-2015-8442, CVE-2015-8447, CVE-2015-8448, CVE-2015-8449, CVE-2015-8450, CVE-2015-8452, and CVE-2015-8454.

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

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution via unspecified vectors. The vulnerability stems from accessing memory after it has been freed, enabling attackers to potentially execute arbitrary code on affected systems.

MitigationUpdate Adobe Flash Player to version 18.0.0.268/20.0.0.228 or later, and Adobe AIR to 20.0.0.204 or later; alternatively, remove Flash Player entirely as it reached end-of-life in 2020.

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
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 Control Panel > Programs and Features, look for 'Adobe Flash Player' or check the version via the Flash Player About page (right-click on Flash content in browser > About Adobe Flash Player). Alternatively, check the file version of npapi.dll or pepflashplayer.dll in the browser's plugins directory.
    Affected if The installed version matches any of these: <= 11.2.202.548, <= 18.0.0.261, 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
    Look in /Library/Internet Plug-Ins/ for 'Flash Player.plugin' and check its Info.plist for CFBundleVersion, or use the Flash Player About dialog in Safari.
    Affected if The installed version matches any of these: <= 11.2.202.548, <= 18.0.0.261, 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  3. Check Adobe AIR version on Windows
    Open Control Panel > Programs and Features, look for 'Adobe AIR' and note its version, or check the file version of 'Adobe AIR.exe' in the installation directory (typically C:\Program Files\Adobe\Adobe AIR).
    Affected if The installed version is <= 19.0.0.241
  4. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory and check the version file or the 'AIR SDK Read Me.txt' for the version number. Common paths include C:\Program Files (x86)\Adobe\Adobe AIR SDK or within an IDE like Flash Builder.
    Affected if The installed version is <= 19.0.0.241
  5. Check if Flash Player or AIR content is being processed
    Review active browser extensions or installed software that handles SWF or FLV content. Check for applications that embed Flash Player (npapi/peppier) or AIR-based applications running on the system.
    Affected if Any Flash-based content, AIR applications, or development tools using the affected SDK versions are in use on the system.

The system is affected if Adobe Flash Player version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or any of 19.0.0.185/207/226/245; or if Adobe AIR or AIR SDK version is 19.0.0.241 or earlier.

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/20.0.0.228 or later, and Adobe AIR to 20.0.0.204 or later; alternatively, remove Flash Player entirely as it reached end-of-life in 2020.

Recommended fix High confidence

Flash Player 18.0.0.268 or later (Windows/OS X), Flash Player 20.0.0.228 or later (19.x/20.x), Flash Player 11.2.202.554 or later (Linux), Adobe AIR 20.0.0.204 or later, Adobe AIR SDK 20.0.0.204 or later, Adobe AIR SDK & Compiler 20.0.0.204 or later

  1. Identify the exact version of Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler currently installed
  2. Navigate to the Adobe Security Bulletin APSB15-32 at https://helpx.adobe.com/security/products/flash-player/apsb15-32.html
  3. Download the appropriate fixed version based on your platform: For Windows/OS X Flash Player, upgrade to 18.0.0.268 (for 18.x) or 20.0.0.228 (for 19.x/20.x); For Linux Flash Player, upgrade to 11.2.202.554; For Adobe AIR, upgrade to 20.0.0.204; For Adobe AIR SDK, upgrade to 20.0.0.204; For Adobe AIR SDK & Compiler, upgrade to 20.0.0.204
  4. Close all browser instances and applications using Flash or AIR
  5. Install the downloaded update
  6. Verify the installed version matches the expected fixed version
  7. Restart any affected applications or browsers
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating to HTML5 alternatives as continued use poses additional security risks

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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