Flash PlayerApplication · Adobe

CVE-2015-5567

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

NVD · unedited

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 allow attackers to execute arbitrary code or cause a denial of service (stack memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5579.

Technical summary

dbcve analysis · high confidence

Adobe Flash Player and Adobe AIR versions before 18.0.0.241 (Windows/OS X), 11.2.202.521 (Linux), and 19.0.0.190 (AIR) contain unspecified vulnerabilities allowing stack memory corruption that can lead to arbitrary code execution or denial of service.

MitigationUpdate Adobe Flash Player to version 18.0.0.241/19.0.0.185 or later (11.2.202.521 for Linux) and Adobe AIR to 19.0.0.190 or later across all affected systems.

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:<= 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= 16.0.0.235

AirApplication

Affected:<= 18.0.0.143<= 18.0.0.199

AndroidOperating system

Affected:all versions

Air SdkApplication

Affected:<= 18.0.0.199

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/OS X

Open Windows Settings > Apps & Features (or Programs and Features), look for 'Adobe Flash Player XX' or check in browser: Chrome (chrome://components), Firefox (Add-ons > Plugins), Edge (Settings > About). On macOS, check /Library/Application Support/Adobe/Flash Player/ or browser plugin settings.

Affected if Version is <= 13.0.0.289, OR equals any of: 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, 16.0.0.235, OR is below 18.0.0.241 (Windows/OS X)
Check Adobe Flash Player version on Linux

Open terminal and run: rpm -q flash-plugin or dpkg -l | grep -i flash, or check /usr/lib/flash-plugin/ directory, or in browsers via about:addons (Firefox) or chrome://plugins (Chrome).

Affected if Version is below 11.2.202.521 on Linux systems
Check Adobe AIR version

Open Control Panel > Programs and Features (Windows), or Applications folder (macOS), or run 'air -version' from command line. On Linux, check /opt/Adobe AIR/ or run: dpkg -l | grep -i adobe-air

Affected if Version is <= 18.0.0.143 or <= 18.0.0.199 (depends on platform) or below 19.0.0.190
Check Adobe AIR SDK version

Look in the SDK installation directory for the AIR SDK version file, or check the filename of the SDK zip file used for installation. Common paths: /path/to/air-sdk/readme.txt or look for version in SDK descriptor files.

Affected if AIR SDK version is <= 18.0.0.199
Check Adobe AIR SDK & Compiler version

Inspect the SDK folder name or version file in the AIR SDK with Compiler installation directory. The version is typically embedded in the SDK folder name or version.xml file.

Affected if AIR SDK & Compiler version is <= 18.0.0.180
Check for Adobe Flash on Google Android

Flash Player is no longer supported on Android. Check if Flash Player APK is installed on Android devices via Settings > Apps > Adobe Flash Player, or via adb: adb shell pm list packages | grep -i adobe

Affected if Adobe Flash Player APK is installed on any Android device (all versions affected)

Any installed version of Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler that matches the affected version ranges listed, or Flash Player present on any Android device, indicates the system is vulnerable to CVE-2015-5567.

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

Remediation

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/19.0.0.185 or later (11.2.202.521 for Linux) and Adobe AIR to 19.0.0.190 or later across all affected systems.

Recommended fix High confidence

Flash Player 18.0.0.241 (or 19.0.0.185 for 19.x) on Windows/OS X, 11.2.202.521 on Linux; AIR 19.0.0.190 (including AIR SDK and AIR SDK & Compiler)

Identify the current Adobe Flash Player version (via browser's plugin page or Windows Control Panel).
Identify the current Adobe AIR version (via AIR settings or program list).
Download the patched Flash Player installer from the Adobe security bulletin APSB15-23: version 18.0.0.241 for Windows/OS X or 11.2.202.521 for Linux.
Download the patched Adobe AIR runtime (version 19.0.0.190) and, if used, the corresponding AIR SDK and AIR SDK & Compiler.
Uninstall the existing Flash Player and AIR installations.
Install the new Flash Player version (18.0.0.241 / 11.2.202.521) and AIR version 19.0.0.190.
Restart any browsers or applications that use Flash or AIR to ensure the new version is loaded.
On Android, where Adobe no longer supports Flash, uninstall or disable the Flash plugin entirely.

Caveat Potential minor compatibility issues with legacy Flash content; otherwise no major breaking changes

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-5567 — 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-5567 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-5567?

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.199 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 3.8%

Affects: Flash Player

Remediation

A high-priority fix

Fix this in Flash Player 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

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