CVE-2015-5559
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.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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-5127, CVE-2015-5130, CVE-2015-5134, CVE-2015-5539, CVE-2015-5540, CVE-2015-5550, CVE-2015-5551, CVE-2015-5556, CVE-2015-5557, CVE-2015-5561, CVE-2015-5563, CVE-2015-5564, and CVE-2015-5565.
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 confidenceUse-after-free vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution via unspecified vectors. Memory corruption occurs when the application attempts to access memory after it has been freed, enabling attackers to inject and execute malicious code.
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.
-
Identify installed Adobe productsCheck system for Adobe Flash Player, Adobe AIR, or Adobe AIR SDK installations. On Windows, inspect Program Files for Adobe folders, check registry under HKLM\SOFTWARE\Macromedia\FlashPlayer and HKLM\SOFTWARE\Adobe\AIR, or look for the Flash Player plugin in browser directories.Affected if Any of these products are present on the system
-
Determine Adobe Flash Player versionFor browser plugin: Visit Adobe's version check page or enter 'about:flash' in Firefox address bar. For ActiveX (IE): Check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. Compare the version number against 11.2.202.491 and 18.0.0.209.Affected if Version is 11.2.202.491 or earlier, OR version is 18.0.0.209 or earlier (but above 11.2.x)
-
Determine Adobe AIR versionOpen Windows Control Panel > Programs and Features, locate Adobe AIR entry and note the version. Alternatively, check registry HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AdobeAIR or inspect the version.properties file in the AIR installation directory.Affected if Version is 18.0.0.180 or earlier
-
Determine Adobe AIR SDK versionIf Adobe AIR SDK or AIR SDK & Compiler is installed, locate the SDK installation directory and check the version.txt or AIR SDK readme file. Common paths include C:\Program Files (x86)\Adobe\AIR SDK or C:\AIR_SDK directory.Affected if SDK version is 18.0.0.180 or earlier
The environment is affected if Adobe Flash Player version is <= 11.2.202.491 or <= 18.0.0.209, OR if Adobe AIR/AIR SDK version is <= 18.0.0.180, and the affected component is actively used.
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 18.0.0.232+ (Windows/OS X) or 11.2.202.508+ (Linux), and Adobe AIR to 18.0.0.199+. Alternatively, retire Flash Player if no longer required, as Adobe End-of-Life was December 2020.
Flash Player 18.0.0.232+ (Windows/OS X), Flash Player 11.2.202.508+ (Linux), AIR 18.0.0.199+
- Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' or checking the version in add-ons
- For Windows and OS X: Download and install Flash Player version 18.0.0.232 or later from the Adobe website
- For Linux: Download and install Flash Player version 11.2.202.508 or later from the Adobe website
- For Adobe AIR: Download and install AIR version 18.0.0.199 or later from the Adobe website
- For Adobe AIR SDK or AIR SDK & Compiler: Download and install version 18.0.0.199 or later from the Adobe developer website
- Restart any affected browsers or applications after upgrading
- Verify the installed version matches or exceeds the fixed version numbers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5559 — 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-5559 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