CVE-2015-8070
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.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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-8048, CVE-2015-8049, CVE-2015-8050, CVE-2015-8055, CVE-2015-8056, CVE-2015-8057, CVE-2015-8058, CVE-2015-8059, CVE-2015-8061, CVE-2015-8062, CVE-2015-8063, CVE-2015-8064, CVE-2015-8065, CVE-2015-8066, CVE-2015-8067, CVE-2015-8068, CVE-2015-8069, CVE-2015-8071, CVE-2015-8401, CVE-2015-8402, CVE-2015-8403, CVE-2015-8404, CVE-2015-8405, CVE-2015-8406, CVE-2015-8410, CVE-2015-8411, CVE-2015-8412, CVE-2015-8413, CVE-2015-8414, CVE-2015-8420, CVE-2015-8421, CVE-2015-8422, CVE-2015-8423, CVE-2015-8424, CVE-2015-8425, CVE-2015-8426, CVE-2015-8427, CVE-2015-8428, CVE-2015-8429, CVE-2015-8430, CVE-2015-8431, CVE-2015-8432, CVE-2015-8433, CVE-2015-8434, CVE-2015-8435, CVE-2015-8436, CVE-2015-8437, CVE-2015-8441, CVE-2015-8442, CVE-2015-8447, CVE-2015-8448, CVE-2015-8449, CVE-2015-8450, CVE-2015-8452, and CVE-2015-8454.
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 allows remote attackers to execute arbitrary code by exploiting improper memory management in the affected software versions.
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.548<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245<= 19.0.0.241<= 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 the installed Adobe Flash Player versionIn a web browser, navigate to 'About Adobe Flash Player' (right-click on Flash content and select 'About Adobe Flash Player'), or visit a version detection page. On Windows, also check the version in Add/Remove Programs or the version file in the installation directory.Affected if The displayed version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
-
Identify the installed Adobe AIR versionOn Windows, open Control Panel and look in Add/Remove Programs for 'Adobe AIR'. On macOS, check /Applications/Adobe AIR Installer.app or the Applications folder. The version is typically displayed in the installer or in system settings.Affected if The installed Adobe AIR version is 19.0.0.241 or earlier.
-
Identify the Adobe AIR SDK version in useIf you are a developer using the Adobe AIR SDK, check the SDK version by looking at the 'air-sdk-version' file or the 'VERSION' file in the SDK installation directory, or check the release notes included with the SDK.Affected if The Adobe AIR SDK or Adobe AIR SDK & Compiler version is 19.0.0.241 or earlier.
-
Confirm the vulnerability is exploitable only when Flash Player or AIR handles specific contentNote that this use-after-free vulnerability is triggered when Adobe Flash Player or Adobe AIR processes maliciously crafted content. Ensure you are not loading untrusted SWF files or content from untrusted sources.Affected if You regularly view or interact with SWF content from the web or untrusted sources using a vulnerable version.
You are affected if any installed Adobe Flash Player version falls within the specified affected ranges or if any installed Adobe AIR or AIR SDK version is 19.0.0.241 or earlier.
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 · scopedApply vendor-provided patches by updating Flash Player to version 18.0.0.268/20.0.0.228 or later (11.2.202.554+ on Linux), and Adobe AIR to version 20.0.0.204 or later.
Flash Player 18.0.0.268+/20.0.0.228+/11.2.202.554+; Adobe AIR 20.0.0.204+; Adobe AIR SDK 20.0.0.204+
- Identify the specific Adobe Flash Player or AIR product and version currently installed
- Navigate to the Adobe security bulletin APSB15-32 at https://helpx.adobe.com/security/products/flash-player/apsb15-32.html
- Download the appropriate fixed version based on your product: Flash Player 18.0.0.268 or later for version 18.x; Flash Player 20.0.0.228 or later for versions 19.x/20.x; Flash Player 11.2.202.554 or later for Linux; Adobe AIR 20.0.0.204 or later; Adobe AIR SDK 20.0.0.204 or later
- Close all browsers and applications using Flash Player or AIR
- Install the updated version following Adobe's standard installation process
- Verify the version has been updated successfully
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-8070 — 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-8070 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