dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-8419

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-8443, CVE-2015-8444, CVE-2015-8451, and CVE-2015-8455.

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 Adobe AIR allowing arbitrary code execution or denial of service. Affects specific versions across Windows, OS X, and Linux platforms via unspecified attack vectors.

MitigationUpdate Adobe Flash Player to 18.0.0.268 (18.x), 20.0.0.228 (19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR to 20.0.0.204. If Flash Player cannot be updated, uninstall or disable it as it reached end-of-life in December 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
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 if Adobe Flash Player is installed
    Windows: Open Control Panel > Programs and Features, look for Adobe Flash Player. macOS: Check /Applications for Adobe Flash Player or run 'system_profiler SPApplicationsDataType | grep -i Flash'. Linux: Run 'rpm -qa | grep -i flash' or 'dpkg -l | grep -i flash'
    Affected if Adobe Flash Player is present on the system
  2. Determine Adobe Flash Player version on Windows
    Open Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion (32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\CurrentVersion (64-bit), read the Version value
    Affected if 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/19.0.0.245
  3. Determine Adobe Flash Player version on macOS
    If installed in Applications, right-click Adobe Flash Player.app > Get Info, or check the version via terminal: 'defaults read /Applications/Adobe\ Flash\ Player.app/Contents/Info CFBundleVersion'
    Affected if 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/19.0.0.245
  4. Determine Adobe Flash Player version on Linux
    Check the Flash plugin version in browser, or run 'rpm -q flash-plugin' or 'dpkg -l | grep flash', or examine the file /usr/lib/flash-plugin/libflashplayer.so version info
    Affected if Version is 11.2.202.548 or lower (Linux-specific 11.2.x branch)
  5. Check if Adobe AIR is installed and its version
    Windows: Open Control Panel > Programs and Features, look for Adobe AIR. macOS: Check /Applications for Adobe AIR or run 'system_profiler SPApplicationsDataType | grep -i AIR'. Run 'air -version' if AIR SDK is installed. Check registry HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR for Version
    Affected if Adobe AIR version is 19.0.0.241 or lower

The system is affected if Adobe Flash Player version falls within the listed vulnerable ranges (11.2.202.548 or lower, 18.0.0.261 or lower, or any of 19.0.0.185/207/226/245) OR Adobe AIR version is 19.0.0.241 or lower.

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 18.0.0.268 (18.x), 20.0.0.228 (19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR to 20.0.0.204. If Flash Player cannot be updated, uninstall or disable it as it reached end-of-life in December 2020.

Recommended fix High confidence

Flash Player 20.0.0.228+ (Windows/OS X), Flash Player 11.2.202.554+ (Linux), AIR 20.0.0.204+, AIR SDK 20.0.0.204+

  1. Identify the currently installed Adobe Flash Player or AIR version from 'Add or Remove Programs' or by visiting the Adobe version check page
  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 for your platform: Flash Player 20.0.0.228 or later for Windows/OS X, Flash Player 11.2.202.554 or later for Linux, or AIR 20.0.0.204 or later
  4. Close all web browsers and applications that use Flash Player or AIR
  5. Run the Adobe installer for the new version
  6. Restart web browsers after installation completes
  7. Verify the installed version matches the fixed release using the Adobe version check page
Caveat Flash Player and AIR reached end-of-life on December 31, 2020; no further security updates will be provided; 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
  • 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-8419 — 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-8419 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