CVE-2015-8444
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.268 and 19.x and 20.x before 20.0.0.228 on Windows and OS X and before 11.2.202.554 on Linux, Adobe AIR before 20.0.0.204, Adobe AIR SDK before 20.0.0.204, and Adobe AIR SDK & Compiler before 20.0.0.204 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-8045, CVE-2015-8047, CVE-2015-8060, CVE-2015-8408, CVE-2015-8416, CVE-2015-8417, CVE-2015-8418, CVE-2015-8419, CVE-2015-8443, CVE-2015-8451, and CVE-2015-8455.
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 confidenceMemory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. This is one of multiple critical memory corruption flaws discovered in Flash Player around late 2015.
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<= 19.0.0.241<= 19.0.0.241<= 19.0.0.241<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245<= 11.2.202.548CVSS 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 Windows Flash Player versionOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player or check the version property of npapi.dll or pepflashplayer.dll in the Flash Player installation directory (typically C:\Windows\System32\Macromed\Flash)Affected if The version is 18.0.0.261 or lower; or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245; or 11.2.202.548 or lower
-
Check macOS Flash Player versionOpen Finder, go to /Library/Internet Plug-Ins/ and right-click Flash Player.plugin to Get Info, or run 'defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion' in TerminalAffected if The version is 18.0.0.261 or lower; or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245; or 11.2.202.548 or lower
-
Check Adobe AIR version on WindowsOpen Programs and Features (or Add/Remove Programs), locate Adobe AIR in the list, and note the version shown; alternatively check the version in the AIR runtime installation directoryAffected if The version is 19.0.0.241 or lower
-
Check Adobe AIR SDK versionIf using the AIR SDK for development, locate the AIR SDK folder and check the version.properties or VERSION file, or run 'air-sdk-version' command if available in the SDK bin directoryAffected if The SDK version is 19.0.0.241 or lower
You are affected if any installed Adobe Flash Player matches the vulnerable 18.x/19.x/11.2.x versions or any Adobe AIR/SDK version is 19.0.0.241 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 to version 18.0.0.268 or later (20.0.0.228 for versions 19.x/20.x) and Adobe AIR to 20.0.0.204 or later. If Flash is not required, consider removing it entirely to eliminate the attack surface.
Adobe Flash Player 20.0.0.228+ (Windows/OS X), 18.0.0.268+ (18.x branch), 11.2.202.554+ (Linux); Adobe AIR 20.0.0.204+; Adobe AIR SDK 20.0.0.204+; Adobe AIR SDK & Compiler 20.0.0.204+
- Identify which Adobe product is installed: Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler
- Determine the current version of the installed Adobe product
- For Flash Player on Windows/OS X: upgrade to version 20.0.0.228 or later
- For Flash Player 18.x: upgrade to version 18.0.0.268 or later
- For Flash Player on Linux: upgrade to version 11.2.202.554 or later
- For Adobe AIR: upgrade to version 20.0.0.204 or later
- For Adobe AIR SDK: upgrade to version 20.0.0.204 or later
- For Adobe AIR SDK & Compiler: upgrade to version 20.0.0.204 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8444 — 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-8444 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