Flash PlayerApplication · Adobe

CVE-2015-5560

HIGH · 10.0 CVSS v2.0 Published 2015-08-14

Fix available

A fix is available. Upgrade to after 18.0.0.209 or later.

See remediation →

100/100

Remediation priority · Urgent

High EPSS Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Integer overflow in Adobe Flash Player before 18.0.0.232 on Windows and OS X and before 11.2.202.508 on Linux, Adobe AIR before 18.0.0.199, Adobe AIR SDK before 18.0.0.199, and Adobe AIR SDK & Compiler before 18.0.0.199 allows attackers to execute arbitrary code via unspecified vectors.

Technical summary

dbcve analysis · high confidence

Integer overflow vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution. The vulnerability exists in versions before 18.0.0.232 (Windows/OS X), 11.2.202.508 (Linux), and before 18.0.0.199 for AIR products. Attackers can exploit this memory corruption flaw to execute arbitrary code remotely.

MitigationUpdate Adobe Flash Player to version 18.0.0.232 or later (or migrate away from Flash given its end-of-life status), and update Adobe AIR to 18.0.0.199 or later. Given Flash is deprecated, consider migration to HTML5 as the long-term solution.

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:<= 11.2.202.491<= 18.0.0.209

AirApplication

Affected:<= 18.0.0.180

Air SdkApplication

Affected:<= 18.0.0.180

Air Sdk \& CompilerApplication

Affected:<= 18.0.0.180

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.

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), or check the version via the Adobe Flash Player check page at about:flash in Internet Explorer, or review the flashplayerplugin_*.exe file version in %windir%\System32\Macromed\Flash or %windir%\SysWOW64\Macromed\Flash

Affected if Version is 11.2.202.491 or earlier, or between 11.2.202.500 and 18.0.0.209 inclusive (18.x versions before 18.0.0.232)
Check Adobe Flash Player version on macOS

Navigate to /Library/Application Support/Adobe/Flash Player/ and locate the version file, or check the Flash Player.plugin version info in /Library/Internet Plug-Ins/

Affected if Version is 11.2.202.491 or earlier, or between 11.2.202.500 and 18.0.0.209 inclusive (18.x versions before 18.0.0.232)
Check Adobe Flash Player version on Linux

Use the command 'rpm -q flash-plugin' or check the version file in /usr/lib/flash-plugin/ or /opt/flash-plugin/

Affected if Version is 11.2.202.508 or earlier (Linux-specific threshold)
Check Adobe AIR version installed

Open Windows Control Panel > Programs and Features and look for Adobe AIR, or check the version in the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\Version, or on macOS check /Applications/Adobe AIR Installer.app

Affected if Version is 18.0.0.180 or earlier (or any version before 18.0.0.199)
Check Adobe AIR SDK version

Locate the AIR SDK installation directory and open the readme.txt or version file, or check the SDK's release notes; the version is typically visible in the SDK folder name or in a version.properties file

Affected if Version is 18.0.0.180 or earlier (for AIR SDK or AIR SDK & Compiler)
Verify Flash Player is enabled in browsers

In Internet Explorer, go to Manage Add-ons > Shockwave Flash Object; in Chrome, enter chrome://plugins and locate Flash; in Firefox, go to Add-ons > Plugins; in Edge (legacy), go to about:addons

Affected if Flash Player is enabled and the vulnerable version is installed (exploitation requires Flash to be active)

A user is affected if Adobe Flash Player version is at or below 11.2.202.491, 18.0.0.209 or below (18.x), or 11.2.202.508 or below on Linux, OR if Adobe AIR/AIR SDK is version 18.0.0.180 or below, and the software is present and enabled in the environment.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 18.0.0.209

Vendor patch helpx.adobe.com →

Interim mitigation

Update Adobe Flash Player to version 18.0.0.232 or later (or migrate away from Flash given its end-of-life status), and update Adobe AIR to 18.0.0.199 or later. Given Flash is deprecated, consider migration to HTML5 as the long-term solution.

Recommended fix High confidence

Flash Player 18.0.0.232 (Windows/OS X) or 11.2.202.508 (Linux); Adobe AIR 18.0.0.199; Adobe AIR SDK 18.0.0.199; Adobe AIR SDK & Compiler 18.0.0.199

Identify the installed Adobe Flash Player version by navigating to About Flash Player in the software
Download the appropriate fixed version from Adobe's official security bulletin (APSB15-19): Flash Player 18.0.0.232 for Windows/OS X, or Flash Player 11.2.202.508 for Linux
Close all browsers and applications that use Flash Player
Install the updated Flash Player version
For Adobe AIR users, upgrade to version 18.0.0.199 or later
For Adobe AIR SDK and AIR SDK & Compiler users, upgrade to version 18.0.0.199 or later
Restart browsers and verify the update was applied successfully

Caveat Minor compatibility issues may occur with older Flash content using deprecated APIs; some enterprise environments may require testing before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flash Player Scoped from the published advisory

Consultation4.0 h
Implementation2.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,970

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2015-5560 — 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-5560 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-5560?

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 18.0.0.209 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 66.0%

Affects: Flash Player

Remediation

A high-priority fix

Fix this in Flash Player 11 hrs · High

Typical engagement from $1,970

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-5560 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