CVE-2015-5582
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-5580, 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 confidenceAdobe Flash Player and AIR contained a memory corruption vulnerability allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. This affected Flash Player versions prior to 18.0.0.241/19.0.0.185 (Windows/OS X) and 11.2.202.521 (Linux), plus AIR versions before 19.0.0.190.
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.143<= 18.0.0.199all versions<= 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.246<= 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 if Adobe Flash Player is installedOn Windows, check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer or inspect the npapi plugin file (flash*.ocx) in browser plugin folders. On Mac, check /Library/Internet Plug-Ins/Flash Player.plugin. On Linux, check /usr/lib/flash-plugin/ or run dpkg -l | grep flashAffected if Flash Player is installed and its version falls within the affected ranges: <= 11.2.202.508, <= 13.0.0.289, or any of the specific versions listed (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)
-
Check Adobe Flash Player version via browserVisit Adobe's version check page at https://helpx.adobe.com/flash-player.html or enter about:plugins in Firefox address bar to view installed plugin versionsAffected if The reported version is earlier than 18.0.0.241 (Windows/OS X) or earlier than 11.2.202.521 (Linux)
-
Check if Adobe AIR runtime is installedOn Windows, look for Adobe AIR in Add/Remove Programs or check C:\Program Files (x86)\Adobe\Adobe AIR\Versions\. On Mac, check /Applications/Adobe AIR Installer.appAffected if Adobe AIR is installed with version <= 18.0.0.143 or <= 18.0.0.199 (specific version ranges vary by release channel)
-
Check Adobe AIR SDK installationIf you are a developer using the AIR SDK, locate the SDK directory and open the AIR SDK descriptor file (version.xml) or check the SDK's readme/version file. Common paths: C:\Program Files\Adobe\AIR SDK or within your IDE's SDK configurationAffected if AIR SDK version <= 18.0.0.199 or AIR SDK & Compiler version <= 18.0.0.180 is in use
-
Check for Flash-based content on AndroidIf the system is Google Android, note that all versions of Flash for Android are affected. Verify whether Flash Player for Android (APK) was ever installed on the deviceAffected if Flash Player for Android is or was installed on any Android device, since all Android versions of Flash are in the affected range
You are affected if Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK is installed with a version that matches or falls below the affected version numbers listed for this CVE.
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 to Adobe Flash Player 18.0.0.241/19.0.0.185 or later (Windows/OS X), 11.2.202.521 or later (Linux), or AIR 19.0.0.190 or later. Since Flash is end-of-life, consider migrating away from Flash-based applications entirely.
Flash Player 18.0.0.241 (or 19.0.0.185 for 19.x), 11.2.202.521 on Linux; AIR 19.0.0.190; AIR SDK 19.0.0.190; AIR SDK & Compiler 19.0.0.190
- Identify the installed version of Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler on the target system.
- For Flash Player on Windows or macOS: download and install version 18.0.0.241 (or version 19.0.0.185 if you are using the 19.x branch) from the official Adobe Flash Player download page.
- For Flash Player on Linux: download and install version 11.2.202.521 from the Adobe site.
- For Adobe AIR: upgrade to version 19.0.0.190 (or later).
- For Adobe AIR SDK: upgrade to version 19.0.0.190 (or later).
- For Adobe AIR SDK & Compiler: upgrade to version 19.0.0.190 (or later).
- On Android devices: uninstall or disable the Flash Player plugin, as Adobe no longer provides security updates for Android.
- After installation, verify the version through the Flash Player About dialog or by checking the AIR SDK version file.
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-5582 — 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-5582 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