Flash PlayerApplication · Adobe

CVE-2015-5587

HIGH · 10.0 CVSS v2.0 Published 2015-09-22
Fix available
A fix is available. Upgrade to after 18.0.0.199 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
Stack-based buffer overflow in Adobe Flash Player before 18.0.0.241 and 19.x before 19.0.0.185 on Windows and OS X and before 11.2.202.521 on Linux, Adobe AIR before 19.0.0.190, Adobe AIR SDK before 19.0.0.190, and Adobe AIR SDK & Compiler before 19.0.0.190 allows attackers to execute arbitrary code via unspecified vectors.

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

Stack-based buffer overflow in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability affects Flash Player versions before 18.0.0.241 and 19.x before 19.0.0.185 on Windows/OS X, and before 11.2.202.521 on Linux, as well as Adobe AIR and SDK versions before 19.0.0.190.

MitigationUpdate Adobe Flash Player to version 18.0.0.241 or later (19.x to 19.0.0.185) and Adobe AIR/SDK to version 19.0.0.190 or later across all affected endpoints.

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.508<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246
AirApplication
Affected:<= 18.0.0.143<= 18.0.0.199
Air SdkApplication
Affected:<= 18.0.0.199
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.180

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 Registry Editor and 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 The version listed is less than 18.0.0.241, or is 19.x but less than 19.0.0.185, or is 11.x but less than 11.2.202.521, or matches any of the specific versions listed (14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246)
  2. Check Adobe Flash Player version on Linux
    Locate the Flash Player plugin in /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/. Check the version file or the libflashplayer.so file version using 'rpm -q flash-plugin' or 'dpkg -l flashplugin-installer' depending on the package manager, or inspect the plugin file properties.
    Affected if The installed version is less than 11.2.202.521 or is one of the specific affected versions listed (11.2.202.508, 13.0.0.289)
  3. Check Adobe AIR runtime version on Windows
    Navigate to C:\Program Files\Adobe\Adobe AIR\Versions\ or C:\Program Files (x86)\Adobe\Adobe AIR\Versions\ and locate the AIR runtime folder. Check the version by examining the version.txt file inside the folder, or right-click the Adobe AIR Application Installer.exe and view Properties > Details for the File Version.
    Affected if The version is 18.0.0.143 or lower, or is between 18.0.0.144 and 18.0.0.199 inclusive
  4. Check Adobe AIR SDK version
    Locate the installed AIR SDK directory (commonly in C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\ or under the user's SDK installation path). Check the AIR SDK version by reading the version file or examining the SDK folder name, which typically includes the version number.
    Affected if The SDK version is 18.0.0.199 or lower, or for the AIR SDK and Compiler package, 18.0.0.180 or lower

The environment is affected if any installed instance of Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK matches or falls below the affected version thresholds listed for 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 18.0.0.199
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 18.0.0.241 or later (19.x to 19.0.0.185) and Adobe AIR/SDK to version 19.0.0.190 or later across all affected endpoints.

Recommended fix High confidence

Flash Player: 18.0.0.241+ (Windows/OS X), 19.0.0.185+ (19.x), or 11.2.202.521+ (Linux); AIR/AIR SDK/AIR SDK & Compiler: 19.0.0.190+

  1. 1. Identify the installed Adobe product (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler) and its current version number
  2. 2. For Flash Player on Windows or OS X: upgrade to version 18.0.0.241 or later, or version 19.0.0.185 or later
  3. 3. For Flash Player on Linux: upgrade to version 11.2.202.521 or later
  4. 4. For Adobe AIR: upgrade to version 19.0.0.190 or later
  5. 5. For Adobe AIR SDK: upgrade to version 19.0.0.190 or later
  6. 6. For Adobe AIR SDK & Compiler: upgrade to version 19.0.0.190 or later
  7. 7. Download the appropriate fixed version from Adobe's official security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-23.html
  8. 8. Uninstall the current vulnerable version

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-5587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-5587 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