CVE-2015-8045
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-8047, CVE-2015-8060, CVE-2015-8408, CVE-2015-8416, CVE-2015-8417, CVE-2015-8418, CVE-2015-8419, CVE-2015-8443, CVE-2015-8444, 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 arbitrary code execution or denial of service. Affects Flash Player versions before 18.0.0.268 (all platforms), 19.x/20.x before 20.0.0.228 (Windows/OS X), and before 11.2.202.554 (Linux), as well as Adobe AIR versions before 20.0.0.204.
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<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245<= 11.2.202.548<= 19.0.0.241<= 19.0.0.241CVSS 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 Flash Player versionOpen a browser and navigate to 'about:flash' (Firefox) or 'chrome://components' (Chrome) to see the Flash version. On Windows, also check the file version of C:\Windows\System32\Macromed\Flash\Flash*.ocx or in Control Panel > Programs and Features look for 'Adobe Flash Player XX'Affected if Version is 18.0.0.261 or earlier, or 19.0.0.185/207/226/245, or 19.x/20.x before 20.0.0.228, or 11.2.202.548 or earlier on Linux
-
Identify installed Adobe AIR versionOn Windows, open Control Panel > Programs and Features and look for 'Adobe AIR'. On macOS, check /Applications/Adobe AIR Installer.app. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR" /v Version' in Command Prompt (Windows)Affected if Version is 19.0.0.241 or earlier
-
Identify installed Adobe AIR SDK versionCheck the installation directory (commonly C:\Program Files\Adobe\Adobe AIR SDK or ~/Adobe AIR SDK) for version.txt or the AIR SDK folder name. On Windows, also check Add/Remove Programs for 'Adobe AIR SDK'Affected if Version is 19.0.0.241 or earlier
-
Confirm Flash Player is active in browsersCheck if any browser plugins have Flash enabled. In Chrome, go to chrome://extensions and look for Flash. In Firefox, go to Add-ons > Plugins. If Flash is present and enabled, the vulnerability is reachableAffected if Flash Player plugin is installed and enabled in any browser on the system
The system is affected if Adobe Flash Player version is below 18.0.0.268, or is any 19.x/20.x version below 20.0.0.228, or is 11.2.202.548 or earlier on Linux, or if Adobe AIR or AIR SDK is 19.0.0.241 or earlier, and Flash is actively installed/enabled.
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 · scopedUpgrade to Adobe Flash Player 18.0.0.268/20.0.0.228 or later and Adobe AIR 20.0.0.204 or later. If Flash is not required, consider removing it to reduce attack surface.
Adobe Flash Player 18.0.0.268 / 20.0.0.228 (or 11.2.202.554 for Linux); Adobe AIR 20.0.0.204; Adobe AIR SDK 20.0.0.204; Adobe AIR SDK & Compiler 20.0.0.204
- Identify the exact product installed (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler) and its current version
- Determine the operating system (Windows, OS X, or Linux)
- For Flash Player on Windows/OS X: upgrade to 18.0.0.268 for the 18.x branch or 20.0.0.228 for the 19.x/20.x branches
- For Flash Player on Linux: upgrade to 11.2.202.554
- For AIR runtime: upgrade to 20.0.0.204
- For AIR SDK: upgrade to 20.0.0.204
- For AIR SDK & Compiler: upgrade to 20.0.0.204
- Verify the installation of the correct patched version
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-8045 — 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-8045 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