dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-3105

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
High EPSS 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
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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) 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 confidence

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple product lines across Windows, OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to version 13.0.0.292, 18.0.0.160, or 11.2.202.466 (Linux), and Adobe AIR to 18.0.0.144/143 depending on platform. Remove Flash if unnecessary 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
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
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
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. Identify Adobe Flash Player version on Windows/Mac/Linux
    Open a web browser and visit Adobe's version check page at https://helpx.adobe.com/flash-player.html, or check the Add/Remove Programs entry in Control Panel, or examine the Flash DLL file properties (npctrl.dll or Flash32_XXXXXX.ocx in System32)
    Affected if Version is 11.2.202.460 or lower, 13.0.0.289 or lower, or any of these specific versions: 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, or 15.0.0.246
  2. Identify Adobe AIR version on desktop
    Open Windows Control Panel > Programs and Features, or on Mac check /Library/Frameworks/Adobe AIR.framework, or run 'Adobe AIR Application Installer' and check its version from the Help > About menu
    Affected if Version is 17.0.0.172 or lower, or 17.0.0.144 or lower (specific to certain platforms)
  3. Identify Adobe AIR SDK version
    Check the AIR SDK readme.txt or the version property in the AIR SDK descriptor file, typically found in the SDK installation directory root
    Affected if Version is 17.0.0.172 or lower
  4. Check for Adobe Flash Player on Android devices
    On Android devices, go to Settings > Apps > Downloaded and look for 'Adobe Flash Player' in the app list, or check if any browsers have Flash plugin enabled in settings
    Affected if Any version of Adobe Flash Player for Android is installed or enabled (all Android versions are affected)
  5. Verify if Flash Player NPAPI/PPAPI plugin is enabled in browsers
    In Chrome, navigate to chrome://plugins and verify the Flash Player entry; in Firefox, check Add-ons > Plugins; in Internet Explorer, verify through Manage Add-ons
    Affected if Flash Player plugin is present and enabled in any browser (this is required for the vulnerability to be exploitable)

Your environment is affected if Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Flash for Android is installed at any of the vulnerable versions listed, with the plugin enabled in browsers.

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

Update Adobe Flash Player to version 13.0.0.292, 18.0.0.160, or 11.2.202.466 (Linux), and Adobe AIR to 18.0.0.144/143 depending on platform. Remove Flash if unnecessary given its end-of-life status.

Recommended fix High confidence

Flash Player 18.0.0.160+ (Windows/OS X), 11.2.202.466+ (Linux); Adobe AIR 18.0.0.144+ (Windows), 18.0.0.143+ (OS X/Android)

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to About Flash Player in the player or visiting https://helpx.adobe.com/flash-player.html
  2. 2. For Windows and OS X: Upgrade to Flash Player 18.0.0.160 or later from https://get.adobe.com/flashplayer/
  3. 3. For Linux: Upgrade to Flash Player 11.2.202.466 or later from the Linux YUM repository or Adobe archives
  4. 4. For Adobe AIR (Windows): Upgrade to version 18.0.0.144 or later
  5. 5. For Adobe AIR (OS X/Android): Upgrade to version 18.0.0.143 or later
  6. 6. For Adobe AIR SDK and AIR SDK & Compiler: Apply the corresponding fixed versions (18.0.0.144 for Windows, 18.0.0.143 for OS X)
  7. 7. For Android: Upgrade Adobe AIR to version 18.0.0.143 or later via Google Play Store or appropriate distribution channel
  8. 8. Verify successful installation by checking the updated version number
Caveat Adobe Flash Player reached end-of-life in December 2020; consider migrating to HTML5-based alternatives as this is a deprecated product with no further security updates

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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