AirApplication · Adobe

CVE-2015-5570

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

Use-after-free vulnerability 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, a different vulnerability than CVE-2015-5574, CVE-2015-5581, CVE-2015-5584, and CVE-2015-6682.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR that allows attackers to execute arbitrary code by accessing freed memory. The vulnerability affects specific versions across Windows, OS X, and Linux platforms.

MitigationUpdate Adobe Flash Player to version 18.0.0.241+/19.0.0.185+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR/AIR SDK to 19.0.0.190+. Given the CVSS 10 severity, prioritize immediate patching 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

AirApplication

Affected:<= 18.0.0.199<= 18.0.0.143

Air SdkApplication

Affected:<= 18.0.0.199

Air Sdk \& CompilerApplication

Affected:<= 18.0.0.180

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

AndroidOperating system

Affected:all versions

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.

Identify Adobe Flash Player version on Windows

Open Registry Editor and navigate to HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file version of the Flash Player plugin (flash.ocx or pepflashplayer.dll) in the browser plugins folder

Affected if The version is 13.0.0.289 or earlier, 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, or 16.0.0.235
Identify Adobe Flash Player version on macOS

Open Terminal and run: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion, or right-click the Flash Player.plugin in /Library/Internet\ Plug-Ins/ and select Get Info

Affected if The version is 13.0.0.289 or earlier, OR equals any of the specific 14.x or 15.x versions listed in the affected ranges
Identify Adobe AIR version on Windows or macOS

On Windows, check Add/Remove Programs for Adobe AIR version, or run: C:\Program Files\Adobe\Adobe AIR\Version.dll (right-click > Properties > Details). On macOS, check /Applications/Adobe AIR Installer.app or run: defaults read /Applications/Adobe\ AIR\ Installer.app/Contents/Info CFBundleVersion

Affected if The version is 18.0.0.199 or earlier, OR 18.0.0.143 or earlier for the 18.0.0.x branch
Check for Adobe AIR SDK or Adobe AIR SDK & Compiler installation

Locate the AIR SDK installation directory and check the version file (often version.txt or in the README), or run: adt -version if the AIR SDK is installed and accessible from command line

Affected if The AIR SDK version is 18.0.0.199 or earlier, OR the AIR SDK & Compiler version is 18.0.0.180 or earlier
Check for Flash Player on Google Android devices

On the Android device, go to Settings > Apps > All, and look for any installed Flash Player application (note: Adobe stopped supporting Flash on Android in 2012)

Affected if Flash Player is installed on any version of Google Android (all versions are affected)

A system is affected if it runs any version of Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler matching the specified vulnerable version ranges, or has Flash Player installed on Android.

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+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR/AIR SDK to 19.0.0.190+. Given the CVSS 10 severity, prioritize immediate patching across all affected systems.

Recommended fix High confidence

Flash Player 18.0.0.241+/19.0.0.185+ (Windows/OS X), 11.2.202.521+ (Linux); Adobe AIR 19.0.0.190+; Adobe AIR SDK 19.0.0.190+; Adobe AIR SDK & Compiler 19.0.190+

1. Identify the installed Adobe Flash Player or Adobe AIR version on the system
2. For Windows/OS X systems: upgrade Flash Player to version 18.0.0.241 or later (or 19.0.0.185 or later for the 19.x branch)
3. For Linux systems: upgrade Flash Player to version 11.2.202.521 or later
4. For Adobe AIR installations: upgrade to version 19.0.0.190 or later
5. For Adobe AIR SDK users: upgrade to version 19.0.0.190 or later
6. For Adobe AIR SDK & Compiler users: upgrade to version 19.0.0.190 or later
7. For Android devices: Adobe Flash Player is no longer supported on Android; uninstall and use alternative browser with HTML5 video support
8. Verify the installation of the patched version by checking Help > About Adobe Flash Player (or AIR)

Caveat Flash Player is deprecated and end-of-life as of December 31, 2020; consider migrating to HTML5-based alternatives

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

Fix this in Air Scoped from the published advisory

Consultation4.0 h
Implementation12.0 h
Testing6.0 h
Review / QA3.0 h

25.0 hours of engineering $4,400

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Notes0 Guidelines

Know something about CVE-2015-5570?

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 5.7%

Affects: Air

Remediation

A high-priority fix

Fix this in Air 25 hrs · Moderate

Typical engagement from $4,400

Get a fix See the full breakdown ↓

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