dbcve.org
AirApplication · Adobe

CVE-2015-8067

HIGH · 10.0 CVSS v2.0 Published 2015-12-10
Fix available
A fix is available. Upgrade to after 19.0.0.241 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Use-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-8068, CVE-2015-8069, CVE-2015-8070, 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 confidence

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR that allows attackers to execute arbitrary code via unspecified vectors. The flaw occurs when memory is freed but still accessed, enabling potential code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.268, 19.x/20.x to 20.0.0.228 or later (Linux: 11.2.202.554+), and Adobe AIR/SDK to 20.0.0.204 or later. Consider disabling Flash Player given its end-of-life status.

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
AirApplication
Affected:<= 19.0.0.241
Flash PlayerApplication
Affected:<= 11.2.202.548<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245
Air SdkApplication
Affected:<= 19.0.0.241
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.241

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Flash Player version in browser
    In Internet Explorer, go to Tools > Manage Add-ons > Shockwave Flash Object and note the version. In Chrome, navigate to chrome://plugins and find Flash Player. In Firefox, go to Add-ons > Plugins. Record the full version number displayed.
    Affected if The version is 11.2.202.548 or lower, 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
  2. Check Adobe Flash Player file version on Windows
    Locate the Flash Player DLL file (npctrl.dll for ActiveX, or flash*.ocx). Right-click the file, select Properties, then view the Details tab for the Product Version field.
    Affected if The file version matches any of the affected versions listed above (11.2.x below 202.548, 18.0.x below 0.261, or 19.0.0.185/207/226/245)
  3. Check Adobe AIR version on Windows
    Open the Windows Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR (or similar key containing 'Adobe AIR'). Check the DisplayVersion value.
    Affected if The version is 19.0.0.241 or lower, or the version begins with 19.0.0.x and is at or below 19.0.0.241
  4. Check Adobe AIR SDK version
    If the AIR SDK is installed, locate the SDK directory (commonly in Program Files or a developer tools folder). Look for a version file or check the properties of the AIRSDK.exe or related binaries for the product version.
    Affected if The SDK version is 19.0.0.241 or lower
  5. Verify Flash Player is enabled in the browser
    In each installed browser, check the plugins or add-ons list to confirm Flash Player is currently enabled. In Internet Explorer, go to Manage Add-ons and verify the status. In Chrome and Firefox, check the respective plugin pages.
    Affected if Flash Player is present and enabled in any browser on the system

A system is affected if any installed version of Adobe Flash Player, Adobe AIR, or Adobe AIR SDK matches the vulnerable version ranges, and Flash Player is actively enabled in a browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 19.0.0.241
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 18.0.0.268, 19.x/20.x to 20.0.0.228 or later (Linux: 11.2.202.554+), and Adobe AIR/SDK to 20.0.0.204 or later. Consider disabling Flash Player given its end-of-life status.

Recommended fix High confidence

Flash Player: 18.0.0.268 (18.x) or 20.0.0.228 (19.x/20.x) or 11.2.202.554 (Linux); Adobe AIR: 20.0.0.204

  1. For Flash Player on Windows/OS X running version 18.x: upgrade to Flash Player 18.0.0.268
  2. For Flash Player on Windows/OS X running version 19.x or 20.x: upgrade to Flash Player 20.0.0.228
  3. For Flash Player on Linux: upgrade to Flash Player 11.2.202.554
  4. For Adobe AIR (desktop runtime): upgrade to version 20.0.0.204
  5. For Adobe AIR SDK: upgrade to version 20.0.0.204
  6. For Adobe AIR SDK & Compiler: upgrade to version 20.0.0.204
  7. Obtain updates from the official Adobe Flash Player download page (https://get.adobe.com/flashplayer/) or through your system's software update mechanism
  8. After upgrading, verify the installed version matches the fixed release
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content as modern browsers have removed Flash support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8067 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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