CVE-2015-5562
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.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 allow attackers to execute arbitrary code by leveraging an unspecified "type confusion," a different vulnerability than CVE-2015-5554, CVE-2015-5555, and CVE-2015-5558.
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 · moderate confidenceType confusion vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw affects Flash Player versions prior to 18.0.0.232 (Windows/OS X) and 11.2.202.508 (Linux), as well as AIR versions before 18.0.0.199.
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.209<= 11.2.202.491<= 18.0.0.180<= 18.0.0.180<= 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 on WindowsOpen Control Panel > Programs and Features, look for Adobe Flash Player XX.X.X.XXX entry, or visit https://helpx.adobe.com/flash-player.html and look for the version displayed on the 'About' pageAffected if Version displayed is 18.0.0.209 or lower, or 11.2.202.491 or lower on Linux systems
-
Check Adobe Flash Player version in browsersFor Internet Explorer: open Manage Add-ons > Shockwave Flash Object; for Chrome: type chrome://components in address bar; for Firefox: open Add-ons > PluginsAffected if Shockwave Flash version shown is 18.0.0.209 or lower on Windows/OS X, or 11.2.202.491 or lower on Linux
-
Check Adobe AIR installation and versionOpen Control Panel > Programs and Features (Windows), Applications folder (macOS), or terminal command 'dpkg -l | grep -i air' (Linux) to find installed AIR versionAffected if Adobe AIR version is 18.0.0.180 or lower
-
Check Adobe AIR SDK installationLook for AIR SDK installation directory, typically under C:\Program Files (x86)\Adobe\AIR SDK or /usr/lib/air-sdk on Linux, and open the README or version fileAffected if AIR SDK or AIR SDK & Compiler version is 18.0.0.180 or lower
The environment is affected if any installed Adobe Flash Player version is 18.0.0.209 or lower (Windows/OS X), 11.2.202.491 or lower (Linux), or any Adobe AIR/SDK version is 18.0.0.180 or lower.
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 and Adobe AIR to the specified fixed versions (18.0.0.232/11.2.202.508 and 18.0.0.199 respectively), or uninstall Flash Player if no longer required.
Flash Player 18.0.0.232 (Windows/OS X) / 11.2.202.508 (Linux); AIR 18.0.0.199; AIR SDK 18.0.0.199; AIR SDK & Compiler 18.0.0.199
- 1. Identify the installed Adobe product (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler) and its current version
- 2. For Flash Player on Windows or OS X: upgrade to version 18.0.0.232 or later
- 3. For Flash Player on Linux: upgrade to version 11.2.202.508 or later
- 4. For Adobe AIR: upgrade to version 18.0.0.199 or later
- 5. For Adobe AIR SDK: upgrade to version 18.0.0.199 or later
- 6. For Adobe AIR SDK & Compiler: upgrade to version 18.0.0.199 or later
- 7. Download the appropriate fixed version from the official Adobe security bulletin (apsb15-19) or Adobe's product download pages
- 8. Install the update and restart any affected applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5562 — 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-5562 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