CVE-2015-5584
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 · uneditedUse-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-5570, CVE-2015-5574, CVE-2015-5581, and CVE-2015-6682.
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 confidenceA use-after-free vulnerability in Adobe Flash Player's memory management allows remote attackers to execute arbitrary code by leveraging freed memory before it is properly reallocated. This is a critical memory corruption flaw in the garbage collection or object lifecycle handling of Flash Player and AIR runtime.
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<= 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<= 18.0.0.143<= 18.0.0.199all versions<= 18.0.0.199<= 18.0.0.180CVSS 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.
-
Check Adobe Flash Player version in WindowsOpen Control Panel > Programs and Features, look for Adobe Flash Player in the list, or in Internet Explorer go to Manage Add-ons > Adobe Flash Player. Also check C:\Windows\System32\Macromed\Flash for the DLL version.Affected if The installed version is 13.0.0.289 or earlier, OR exactly matches any of these 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, 15.0.0.246, or 16.0.0.235
-
Check Adobe Flash Player version on macOSOpen System Preferences > Flash Player, or check the library location /Library/Application Support/Adobe/Flash Player for the installed version.Affected if The installed version matches any of the affected versions listed above for your OS version.
-
Check Adobe AIR version on WindowsOpen Control Panel > Programs and Features, look for Adobe AIR. You can also check the version via command line by examining the properties of the Adobe AIR installer or runtime DLL in the installation directory.Affected if The installed version is 18.0.0.143 or earlier, OR is 18.0.0.199 or earlier.
-
Check Adobe AIR version on macOSOpen /Applications/Utilities/Adobe AIR Application Installer to see the version, or check /Library/Frameworks/Adobe AIR.framework for the installed version.Affected if The installed version is 18.0.0.143 or earlier, OR is 18.0.0.199 or earlier.
-
Check Adobe AIR SDK versionIf you use the Adobe AIR SDK for development, check the SDK version by examining the version file or README in the SDK installation directory, typically named with the version number.Affected if The installed SDK version is 18.0.0.199 or earlier, OR the SDK and Compiler version is 18.0.0.180 or earlier.
-
Check for Flash Player on Google AndroidCheck if Flash Player is installed on an Android device by going to Settings > Apps and looking for Adobe Flash Player, or check the version in the app details.Affected if Any version of Adobe Flash Player for Android is installed, as all versions are affected.
A system is affected if it has any version of Adobe Flash Player matching the specific versions listed, Adobe AIR at or below 18.0.0.199, or Adobe Flash Player for Android at any version.
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/19.0.0.185 (Windows/OS X) or 11.2.202.521 (Linux), and Adobe AIR to 19.0.0.190 or later. Consider migrating away from Flash as it is end-of-life.
Flash Player 18.0.0.241+/19.0.0.185+ (Win/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 Player' in the player or checking the system's installed programs
- 2. For Windows/OS X: Upgrade Flash Player to version 18.0.0.241 or later, or version 19.0.0.185 or later
- 3. For Linux: Upgrade Flash Player to version 11.2.202.521 or later
- 4. For Adobe AIR: Upgrade to version 19.0.0.190 or later
- 5. For Adobe AIR SDK: Upgrade to version 19.0.0.190 or later
- 6. For Adobe AIR SDK & Compiler: Upgrade to version 19.0.0.190 or later
- 7. For Android: Upgrade Flash Player for Android to the latest available version from Google Play or Adobe's archive
- 8. Verify the update was successful by checking the Flash Player version again
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-5584 — 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-5584 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