CVE-2015-5558
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-5562.
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 type confusion vulnerability in Adobe Flash Player and AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability affects versions prior to 18.0.0.232 on Windows/OS X, 11.2.202.508 on Linux, and 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<= 11.2.202.491<= 18.0.0.209<= 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 Internet Explorer, right-click on any Flash content (or visit a site with Flash), select 'Run ActiveX Control', then click 'About Adobe Flash Player' in the context menu. Alternatively, check the file version of the ActiveX control at C:\Windows\System32\Macromed\Flash\Flash*.ocxAffected if Version is 11.2.202.491 or earlier, or 18.0.0.209 or earlier on Windows/OS X
-
Check Adobe Flash Player version on macOSOpen Safari or another browser, right-click on Flash content and select 'About Adobe Flash Player', or check the plugin version in the browser's plugin list. The version is typically stored in /Library/Application Support/Adobe/Flash Player/Affected if Version is 18.0.0.209 or earlier (or 11.2.202.491 or earlier for older 11.x releases)
-
Check Adobe Flash Player version on LinuxRun 'rpm -q flash-plugin' or 'dpkg -l libflashplugin-installer' to check the installed package version. Also check the file version of /usr/lib/flash-plugin/libflashplayer.soAffected if Version is 11.2.202.491 or earlier
-
Check Adobe AIR version on Windows or macOSOn Windows, open Add or Remove Programs and look for 'Adobe AIR' or check the version in the installation folder (typically C:\Program Files\Adobe\AIR). On macOS, check /Applications/Adobe AIR Installer.app or run 'defaults read /Applications/Adobe\ AIR\ Installer.app/Contents/Info CFBundleVersion'Affected if Version is 18.0.0.180 or earlier
-
Check Adobe AIR SDK or AIR SDK & Compiler versionLook for the AIR SDK in your development environment. Check the version file or run 'airSDKVersion' if using the SDK. Common locations include Adobe Animate or Adobe Dreamweaver installation directories, or a separately installed AIR SDKAffected if Version string shows 18.0.0.180 or earlier
You are affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches or falls below the affected ranges listed for your platform.
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 AIR to the specified patched versions (18.0.0.232 or later for Flash Player, 18.0.0.199 or later for AIR). Given Flash Player's end-of-life status, consider migrating away from Flash-based content entirely.
Flash Player 18.0.0.232 (Windows/OS X), 11.2.202.508 (Linux); AIR/AIR SDK/AIR SDK & Compiler 18.0.0.199
- Identify which Adobe product is installed (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler)
- Determine the current version installed on the system
- For Flash Player on Windows or OS X: Download and install version 18.0.0.232 or later from adobe.com
- For Flash Player on Linux: Download and install version 11.2.202.508 or later from adobe.com
- For AIR, AIR SDK, or AIR SDK & Compiler: Download and install version 18.0.0.199 or later from adobe.com
- Restart the browser or application after upgrading Flash Player
- Verify the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5558 — 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-5558 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