CVE-2015-5580
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 · uneditedAdobe 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 (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5575, CVE-2015-5577, CVE-2015-5578, CVE-2015-5582, CVE-2015-5588, and CVE-2015-6677.
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 confidenceMemory corruption vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution or denial of service. The vulnerability exists in unspecified vectors within the Flash runtime, enabling attackers to corrupt memory and execute arbitrary code or crash the application.
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<= 18.0.0.199<= 18.0.0.143<= 18.0.0.199<= 18.0.0.180<= 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.246all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Flash Player version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file version of npctrl.dll or flash.ocx in the System32 directory using Properties > DetailsAffected if The version is 11.2.202.508 or earlier, 13.0.0.289 or earlier, or matches any of these exact versions: 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, or 15.0.0.246
-
Identify installed Adobe Flash Player version on LinuxOpen a terminal and run: rpm -q flash-plugin or dpkg -l | grep flash, or check /usr/lib/flash-plugin for the plugin file versionAffected if The version is 11.2.202.508 or earlier (Linux Flash Player is only available as 11.x)
-
Identify installed Adobe Flash Player version on macOSOpen Finder, navigate to /Library/Internet Plug-Ins/ and locate Flash Player.plugin, then right-click and select Get Info to view the version, or use the command: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersionAffected if The version matches any of the vulnerable versions listed for Flash Player (11.x, 13.x, 14.x, or 15.x series)
-
Identify installed Adobe AIR version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\VersionInfo, or check the file version of AIR.dll in the Adobe AIR installation directory (commonly C:\Program Files\Adobe\AIR\Versions\1.0)Affected if The version is 18.0.0.199 or earlier, or 18.0.0.143 or earlier for older release branches
-
Identify installed Adobe AIR SDK versionCheck the AIR SDK version by locating the AIR SDK directory and reading the readme or version file, or run: adt -version if the SDK compiler is installedAffected if The SDK version is 18.0.0.199 or earlier (AIR SDK), or 18.0.0.180 or earlier (AIR SDK and Compiler)
-
Confirm presence of Adobe Flash or AIR on AndroidCheck if Adobe Flash Player or AIR is installed on an Android device by reviewing installed applications in Settings > Apps, or check for /data/data/com.adobe.flashplayer directory on rooted devicesAffected if Adobe Flash Player or AIR is present on any Android device (all Android versions are affected per the CVE)
Your environment is affected if Adobe Flash Player (any version matching 11.2.202.508 or earlier, 13.0.0.289 or earlier, or any of the specific 14.x/15.x versions listed) or Adobe AIR (18.0.0.199 or earlier) is installed and running, or if Flash/AIR exists on Android devices.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Flash Player to version 18.0.0.241+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR to 19.0.0.190+. Organizations still using Flash should migrate to modern web technologies as Flash is end-of-life.
Flash Player 18.0.0.241+ (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.0.190+
- 1. Identify the installed Adobe Flash Player version by navigating to 'about:flash' in the browser or checking Help > About Adobe Flash Player
- 2. Identify the installed Adobe AIR version by checking Help > About Adobe AIR in AIR applications
- 3. For Windows/OS X: Download and install Adobe Flash Player 18.0.0.241 or later (or 19.0.0.185 or later for version 19.x) from the Adobe website
- 4. For Linux: Download and install Adobe Flash Player 11.2.202.521 or later from the Adobe website
- 5. For Adobe AIR: Download and install Adobe AIR 19.0.0.190 or later from the Adobe website
- 6. For Adobe AIR SDK: Download and install Adobe AIR SDK 19.0.0.190 or later from the Adobe developer website
- 7. For Adobe AIR SDK & Compiler: Download and install Adobe AIR SDK & Compiler 19.0.0.190 or later
- 8. For Android: Update Flash Player from Google Play Store to version 19.0.0.190 or later, or uninstall if update unavailable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5580 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5580 in production — separate from our analysis above.
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.
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.
- 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