CVE-2015-8651
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 · uneditedInteger overflow in Adobe Flash Player before 18.0.0.324 and 19.x and 20.x before 20.0.0.267 on Windows and OS X and before 11.2.202.559 on Linux, Adobe AIR before 20.0.0.233, Adobe AIR SDK before 20.0.0.233, and Adobe AIR SDK & Compiler before 20.0.0.233 allows attackers to execute arbitrary code via unspecified vectors.
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 confidenceInteger overflow vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. The vulnerability exists in multiple versions across Windows, OS X, and Linux platforms, and affects both the runtime and SDK components.
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= 5.0= 6.0= 5.0= 6.0= 5.0= 6.0< 20.0.0.233< 20.0.0.233< 11.2.202.559< 18.0.0.324>= 19.0.0.185, < 20.0.0.267< 20.0.0.233= 11.4CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Flash Player version on WindowsOpen a browser and navigate to 'about:flash' in the address bar, or check the version of the Flash NPAPI plugin file (npswf32.dll) or ActiveX control (Flash32_*.ocx) in the system directoryAffected if Version is less than 11.2.202.559, less than 18.0.0.324, or between 19.0.0.185 and 20.0.0.266 inclusive
-
Identify installed Adobe Flash Player version on LinuxCheck the installed flash-plugin package version using the system package manager (rpm or dpkg), or verify the libflashplayer.so file version in the browser plugins directoryAffected if Version is less than 11.2.202.559, less than 18.0.0.324, or between 19.0.0.185 and 20.0.0.266 inclusive
-
Identify installed Adobe Flash Player version on macOSCheck the Flash Player component version in the /Library/Internet Plug-Ins/ directory, or use the Adobe Flash Player Settings managerAffected if Version is less than 11.2.202.559, less than 18.0.0.324, or between 19.0.0.185 and 20.0.0.266 inclusive
-
Identify installed Adobe AIR runtime versionCheck the AIR version through the AIR Settings manager, or locate the AIR runtime installation and inspect its version informationAffected if Version is less than 20.0.0.233
-
Identify installed Adobe AIR SDK versionCheck the AIR SDK version by locating the SDK directory and inspecting the version file or release notes included with the SDK installationAffected if Version is less than 20.0.0.233
-
Check Red Hat Enterprise Linux Flash plugin packageOn RHEL 5 or 6 systems, query the installed flash-plugin package using 'rpm -q flash-plugin' and compare the version against the affected rangesAffected if The system is RHEL 5.0 or 6.0 and has an older Flash plugin installed
A system is affected if Adobe Flash Player version is below 11.2.202.559, below 18.0.0.324, between 19.0.0.185-20.0.0.266, or if Adobe AIR/SDK version is below 20.0.0.233.
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 · scoped11.2.202.55918.0.0.32420.0.0.233
Update Adobe Flash Player to version 18.0.0.324/20.0.0.267 or later, and Adobe AIR to 20.0.0.233 or later. Given Flash Player end-of-life, consider removing Flash entirely if no longer required.
Flash Player 20.0.0.267+ (Windows/OS X), Flash Player 11.2.202.559+ (Linux), Adobe AIR 20.0.0.233+, Adobe AIR SDK 20.0.0.233+
- 1. Identify the currently installed version of Adobe Flash Player or Adobe AIR on the system using 'Add/Remove Programs' or system utilities
- 2. For Flash Player on Windows/OS X: upgrade to version 20.0.0.267 or later from adobe.com
- 3. For Flash Player on Linux: upgrade to version 11.2.202.559 or later from adobe.com
- 4. For Adobe AIR: upgrade to version 20.0.0.233 or later from adobe.com
- 5. For Adobe AIR SDK and AIR SDK & Compiler: upgrade to version 20.0.0.233 or later from adobe.com
- 6. Restart any browsers or applications using Flash Player after the upgrade
- 7. Verify the new version is correctly installed
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-8651 — 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-8651 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