dbcve.org
AirApplication · Adobe

CVE-2015-3106

HIGH · 10.0 CVSS v2.0 Published 2015-06-10
Fix available
A fix is available. Upgrade to after 17.0.0.172 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466 on Linux, Adobe AIR before 18.0.0.144 on Windows and before 18.0.0.143 on OS X and Android, Adobe AIR SDK before 18.0.0.144 on Windows and before 18.0.0.143 on OS X, and Adobe AIR SDK & Compiler before 18.0.0.144 on Windows and before 18.0.0.143 on OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-3103 and CVE-2015-3107.

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, Adobe AIR, and Adobe AIR SDK/Compiler allows attackers to execute arbitrary code. The vulnerability occurs when the software continues using a memory pointer after it has been freed, potentially enabling remote code execution.

MitigationDeploy the patched versions: Flash Player 13.0.0.292/18.0.0.160/11.2.202.466, AIR 18.0.0.144/18.0.0.143, or remove Flash Player if unnecessary as it reached end-of-life.

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:<= 17.0.0.172<= 17.0.0.144
Air SdkApplication
Affected:<= 17.0.0.172
Air Sdk \& CompilerApplication
Affected:<= 17.0.0.172
Flash PlayerApplication
Affected:<= 11.2.202.460<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246
AndroidOperating system
Affected:all versions

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 installed Adobe Flash Player version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\FlashPlayer\CurrentVersion (or HKLM\SOFTWARE\Macromedia\FlashPlayer), or run 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Adobe\FlashPlayer' -ErrorAction SilentlyContinue | Select-Object Version' in PowerShell
    Affected if Version value is less than or equal to 11.2.202.460, less than or equal to 13.0.0.289, or equals 14.0.0.125/145/176/179, 15.0.0.152/167/189/223/239/246
  2. Check Adobe AIR version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR, or run 'Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR' -ErrorAction SilentlyContinue | Select-Object DisplayVersion'
    Affected if DisplayVersion is less than or equal to 17.0.0.172 or 17.0.0.144
  3. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory and check the version file or air-sdk-description.xml, or run 'air -version' if AIR SDK compiler is in PATH
    Affected if SDK version is less than or equal to 17.0.0.172
  4. Check if running on Android device
    On the Android device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Any Android version is running (all versions affected)
  5. Check Flash Player plugin in browsers
    In Chrome, navigate to chrome://components and check Flash Player version; in Firefox, navigate to Add-ons > Plugins; or locate the NPAPI plugin file (NPSWF32.dll) and check its file version
    Affected if Plugin version matches the affected Flash Player versions listed

The environment is affected if any installed version of Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler matches the affected version ranges, or if running on any version of Android with Flash Player.

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 17.0.0.172
Vendor patch helpx.adobe.com →
Interim mitigation

Deploy the patched versions: Flash Player 13.0.0.292/18.0.0.160/11.2.202.466, AIR 18.0.0.144/18.0.0.143, or remove Flash Player if unnecessary as it reached end-of-life.

Recommended fix High confidence

Flash Player 18.0.0.160+ (or 13.0.0.292+ for 13.x branch, 11.2.202.466+ for Linux); Adobe AIR 18.0.0.144+ (Windows) or 18.0.0.143+ (OS X/Android)

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system's installed programs
  2. 2. For Windows/OS X: Navigate to https://get.adobe.com/flashplayer/ and download the latest version (18.0.0.160 or later for the 14.x-18.x branch, or 13.0.0.292 or later for the 13.x branch)
  3. 3. For Linux: Download Flash Player 11.2.202.466 or later from the Adobe archives
  4. 4. For Adobe AIR: Download AIR 18.0.0.144 (Windows) or 18.0.0.143 (OS X/Android) or later from https://get.adobe.com/air/
  5. 5. Close all browser windows and applications using Flash Player before running the installer
  6. 6. Run the installer with administrator privileges
  7. 7. Verify the update was successful by checking the Flash Player version again
Caveat Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content as modern browsers have disabled or removed Flash support

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

Fix this in Air Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3106 — 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-3106 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