Flash PlayerApplication · Adobe

CVE-2015-8410

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

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-8411, 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

dbcve analysis · high confidence

Use-after-free vulnerability in Adobe Flash Player and AIR allowing remote code execution. The flaw occurs when the software continues to use memory after it has been freed, enabling attackers to execute arbitrary code via unspecified vectors.

MitigationUpdate Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (for versions 19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR to version 20.0.0.204 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

Air SdkApplication

Affected:<= 19.0.0.241

Air Sdk \& CompilerApplication

Affected:<= 19.0.0.241

AirApplication

Affected:<= 19.0.0.241

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Adobe Flash Player version

Open a web browser and navigate to 'about:plugins' (Firefox) or 'chrome://plugins' (Chrome) to list installed plugins, or visit a version detection page like 'https://helpx.adobe.com/flash-player.html'. On Windows, also check Programs and Features in Control Panel.

Affected if The displayed version is 18.0.0.261 or lower; or 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245; or 11.2.202.548 or lower (Linux).
Identify installed Adobe AIR version

On Windows, open Control Panel and select 'Programs and Features' to view installed software. On Mac, check the Applications folder for Adobe AIR. You can also run 'Adobe AIR Application Installer' which typically displays the version on launch, or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR.

Affected if The installed Adobe AIR version is 19.0.0.241 or lower.
Identify Adobe AIR SDK version

If you are a developer using the AIR SDK, check the SDK directory: locate the 'AIR SDK Readme.txt' or 'versions.xml' file within the SDK folder. The SDK version is often included in the folder name (for example, an AIR SDK folder may be named 'AIR_SDK_19.0.0.241').

Affected if The AIR SDK version is 19.0.0.241 or lower.

You are affected if Adobe Flash Player is version 18.0.0.261 or lower, any of the specific 19.x versions listed (185, 207, 226, 245), or 11.2.202.548 or lower on Linux; or if Adobe AIR or AIR SDK is version 19.0.0.241 or lower.

Generated from the published advisory. Verify against your own configuration.

Remediation

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 (for versions 19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR to version 20.0.0.204 or later.

Recommended fix High confidence

Flash Player 18.0.0.268+ (18.x branch), 20.0.0.228+ (19.x/20.x branch), 11.2.202.554+ (Linux); AIR/AIR SDK 20.0.0.204+

1. Identify the installed Adobe Flash Player version by navigating to About Flash Player in the browser or checking the system-installed version
2. Identify the installed Adobe AIR version by checking the application's version or the AIR version in the system
3. For Flash Player on Windows and OS X: If using 18.x branch, upgrade to version 18.0.0.268 or later; if using 19.x or 20.x, upgrade to version 20.0.0.228 or later
4. For Flash Player on Linux: Upgrade to version 11.2.202.554 or later
5. For Adobe AIR, Adobe AIR SDK, and Adobe AIR SDK & Compiler: Upgrade to version 20.0.0.204 or later
6. Verify the upgrade was successful by checking the updated version numbers

Caveat Upgrading Flash Player may cause compatibility issues with older SWF content or web applications that rely on specific Flash behavior; AIR upgrades may affect existing AIR application functionality

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
Implementation2.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $890

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8410 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-8410?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 19.0.0.241 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 31.6%

Affects: Flash Player

Remediation

A high-priority fix

Fix this in Flash Player 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-8410 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References