dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8063

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
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-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-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 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 that allows attackers to execute arbitrary code via unspecified vectors. The flaw occurs when memory is freed but still accessed, leading to potential code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.268 or later (Windows/OS X), 11.2.202.554 or later (Linux), or Adobe AIR to 20.0.0.204 or later. Note: Adobe Flash reached end-of-life in December 2020; consider removing Flash entirely if no longer required.

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
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. Identify Adobe Flash Player version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Macromedia\FlashPlayer (for 32-bit) or HKLM\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer (for 64-bit), then check the Version value. Alternatively, locate the Flash Player DLL ( NPSWF32.dll or NPSWF64.dll ) in the browser plugins directory and view its file properties to see the version.
    Affected if The installed version matches one of the affected versions: any version <= 18.0.0.261, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245.
  2. Identify Adobe Flash Player version on Linux
    Check the installed package version using the system package manager. For RPM-based systems, run 'rpm -q flash-player-plugin'. For Debian-based systems, check the installed package with 'dpkg -l | grep flash' or inspect the file /usr/lib/flash-plugin/libflashplayer.so and view its version properties.
    Affected if The installed version is <= 11.2.202.548.
  3. Identify Adobe AIR version on Windows
    Check the Windows Add/Remove Programs list for Adobe AIR, or examine the Adobe AIR executable in its installation directory (typically C:\Program Files\Adobe\Adobe AIR\Versions\) and check the file properties of the runtime binary.
    Affected if The installed version is <= 19.0.0.241.
  4. Identify Adobe AIR SDK version
    Locate the AIR SDK installation directory and check the version file or the AIR SDK descriptor file. The SDK is typically installed to a directory like C:\Program Files (x86)\Adobe\Adobe AIR SDK\ or C:\AIR_SDK\, and contains a version.txt or similar version marker file.
    Affected if The AIR SDK or AIR SDK & Compiler version is <= 19.0.0.241.

If any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version falls within the affected ranges listed, the environment is vulnerable to this CVE.

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 (Windows/OS X), 11.2.202.554 or later (Linux), or Adobe AIR to 20.0.0.204 or later. Note: Adobe Flash reached end-of-life in December 2020; consider removing Flash entirely if no longer required.

Recommended fix High confidence

Adobe Flash Player 18.0.0.268 (or 20.0.0.228 for 19.x/20.x); Adobe AIR 20.0.0.204

  1. Identify the currently installed Adobe Flash Player version (e.g., visit about:flash in a browser or check the Flash Player version in Windows Add/Remove Programs / macOS System Preferences).
  2. Download the patched Adobe Flash Player installer from the official Adobe security bulletin (APSB15‑32) – obtain version 18.0.0.268 (or 20.0.0.228 for 19.x/20.x).
  3. Uninstall the existing Flash Player using the Windows Add/Remove Programs tool, macOS Adobe Flash Player uninstaller, or the Adobe uninstaller utility.
  4. Run the downloaded installer and follow the prompts to install the new Flash Player version.
  5. Restart any open web browsers to ensure the new Flash Player plugin is loaded.
  6. Verify the installed version matches the patched release (18.0.0.268 or 20.0.0.228).
  7. For Adobe AIR, download the AIR SDK 20.0.0.204 from the Adobe security bulletin, update your development environment to use this SDK, and rebuild/re‑package any AIR applications.
Caveat Upgrading Flash Player or AIR may affect compatibility with older content; also note that Adobe Flash Player reached end‑of‑life in December 2020, so consider migrating away.

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