dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-5127

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 Public exploit 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
Use-after-free vulnerability 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, a different vulnerability than CVE-2015-5130, CVE-2015-5134, CVE-2015-5539, CVE-2015-5540, CVE-2015-5550, CVE-2015-5551, CVE-2015-5556, CVE-2015-5557, CVE-2015-5559, CVE-2015-5561, CVE-2015-5563, CVE-2015-5564, and CVE-2015-5565.

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

Use-after-free vulnerability in Adobe Flash Player, Adobe AIR, and Adobe AIR SDK allowing arbitrary code execution. Affects Flash Player versions before 18.0.0.232 (Windows/OS X) and 11.2.202.508 (Linux), and AIR versions before 18.0.0.199. The vulnerability stems from improper memory management where memory is accessed after being freed.

MitigationUpdate Adobe Flash Player, AIR, and AIR SDK to the patched versions specified (18.0.0.232/11.2.202.508 or later). Given Flash Player end-of-life, consider removing Flash entirely and migrating to modern web technologies.

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:<= 18.0.0.209<= 11.2.202.491
EvergreenOperating system
Affected:= 11.4
AirApplication
Affected:<= 18.0.0.180
Air SdkApplication
Affected:<= 18.0.0.180
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. Identify installed Adobe Flash Player version on Windows or macOS
    Open a web browser and visit a Flash version detection page (such as adobe.com/software/flash/about), or check the Flash Player file properties in the installation directory. Alternatively, use the command 'Get-ItemProperty' in PowerShell for system-level installations.
    Affected if The displayed version is 18.0.0.209 or earlier on Windows/OS X, or 11.2.202.491 or earlier on Linux.
  2. Identify installed Adobe Flash Player version on Linux
    Check the installed Flash Player package via the system's package manager (for example, run 'rpm -q flash-player' or 'dpkg -l flashplayer' depending on the distribution).
    Affected if The displayed version is 11.2.202.491 or earlier.
  3. Identify installed Adobe AIR version
    On Windows or macOS, open the Add/Remove Programs control panel or Applications folder to view installed Adobe AIR, or check the AIR application version information in its installation directory. On Linux, use the package manager to query the installed AIR package.
    Affected if The installed version is 18.0.0.180 or earlier.
  4. Identify installed Adobe AIR SDK version
    Locate the Adobe AIR SDK installation directory on the system and check the version information file (such as 'version.xml' or the SDK README), or use the package manager if installed via system packages.
    Affected if The SDK version is 18.0.0.180 or earlier.
  5. Check operating system version on OpenSUSE systems
    Run 'cat /etc/os-release' or 'lsb_release -a' to determine the OpenSUSE version number.
    Affected if The system is running OpenSUSE 11.4 (Evergreen) with Adobe Flash Player or AIR installed.

The environment is affected if any installed Adobe Flash Player, AIR, or AIR SDK version falls within the vulnerable ranges specified, or if running OpenSUSE 11.4 with these products installed.

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.209
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player, AIR, and AIR SDK to the patched versions specified (18.0.0.232/11.2.202.508 or later). Given Flash Player end-of-life, consider removing Flash entirely and migrating to modern web technologies.

Recommended fix High confidence

Flash Player 18.0.0.232 (Windows/OS X), Flash Player 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

  1. Identify all Adobe Flash Player, AIR, AIR SDK, and AIR SDK & Compiler installations on affected systems
  2. Check current version of each installed product
  3. For Flash Player on Windows/OS X: upgrade to version 18.0.0.232 or later
  4. For Flash Player on Linux: upgrade to version 11.2.202.508 or later
  5. For Adobe AIR: upgrade to version 18.0.0.199 or later
  6. For Adobe AIR SDK: upgrade to version 18.0.0.199 or later
  7. For Adobe AIR SDK & Compiler: upgrade to version 18.0.0.199 or later
  8. Download updates from the official Adobe security bulletin (apsb15-19) or Adobe product download pages
Caveat Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based content. No functional breaking changes expected from this security patch.

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5127 — 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-5127 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