dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8455

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
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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-8045, CVE-2015-8047, CVE-2015-8060, CVE-2015-8408, CVE-2015-8416, CVE-2015-8417, CVE-2015-8418, CVE-2015-8419, CVE-2015-8443, CVE-2015-8444, and CVE-2015-8451.

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

Memory corruption vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution via unspecified vectors, distinct from other Flash vulnerabilities discovered in late 2015.

MitigationUpdate Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (or 11.2.202.554 for Linux) and Adobe AIR to 20.0.0.204; consider removing or disabling Flash if updates cannot be applied.

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 Flash Player version in Chrome
    Navigate to chrome://components/ and locate 'Adobe Flash Player' entry, or visit a site like about:flash (if available). Record the version number shown.
    Affected if The listed version is 11.2.202.548 or lower, 18.0.0.261 or lower, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245.
  2. Check Flash Player version in Firefox
    Enter 'about:addons' in the address bar, locate the Flash Player plugin, and note the displayed version number.
    Affected if The listed version matches any of the affected versions listed above.
  3. Check Flash Player version on Windows
    Open Control Panel, navigate to Programs and Features, find Adobe Flash Player (or use the Windows installer version check utility). Alternatively, check the file version of flash32_XX_XX_XX_XX.ocp in the browser plugins folder.
    Affected if The installed version falls within the affected ranges.
  4. Check Adobe AIR installation version
    Open Windows Settings > Apps & Features (or macOS Applications folder), locate Adobe AIR, and note the version. On Windows, also check the file version of AIR.exe in the installation directory.
    Affected if Adobe AIR version is 19.0.0.241 or lower.
  5. Check Adobe AIR SDK version (for developers)
    If you have the AIR SDK installed, locate the SDK folder and open the AIR SDK readme or version file, or run 'airc -version' from the bin directory if available.
    Affected if The AIR SDK or AIR SDK Compiler version is 19.0.0.241 or lower.

If any installed Adobe Flash Player or Adobe AIR version matches or falls within the affected ranges listed, your environment is vulnerable to CVE-2015-8455.

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 11.2.202.554 for Linux) and Adobe AIR to 20.0.0.204; consider removing or disabling Flash if updates cannot be applied.

Recommended fix High confidence

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

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to About Flash Player in the player or checking the version in browser add-ons.
  2. 2. Identify the currently installed Adobe AIR or AIR SDK version from the installed programs list or SDK documentation.
  3. 3. For Flash Player: Download the appropriate fixed version from adobe.com - 18.0.0.268 or later for 18.x, 20.0.0.228 or later for 19.x/20.x on Windows/OS X, or 11.2.202.554 or later for Linux.
  4. 4. For Adobe AIR: Uninstall the current version, then download and install Adobe AIR 20.0.0.204 or later from adobe.com.
  5. 5. For Adobe AIR SDK/Compiler: Download AIR SDK 20.0.0.204 or later from adobe.com and update your development environment.
  6. 6. After installation, verify the version numbers match or exceed the fixed releases specified.
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content

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-8455 — 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-8455 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