dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-3100

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
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
Stack-based buffer overflow 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.

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

A stack-based buffer overflow in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability affects Flash Player versions before 13.0.0.292 and 14.x-18.x before 18.0.0.160 on Windows/OS X, and before 11.2.202.466 on Linux, along with affected AIR versions.

MitigationUpdate Adobe Flash Player to 13.0.0.292/18.0.0.160 or later and Adobe AIR to 18.0.0.144/18.0.0.143 or later. Since Flash Player is end-of-life, consider removing it entirely if not required.

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. Check Adobe Flash Player version on Windows
    Open a browser and navigate to the Adobe Flash Player version check page at https://helpx.adobe.com/flash-player.html, or enter 'about:flash' in the address bar of Internet Explorer. Alternatively, check the version in Control Panel under Programs and Features, looking for Adobe Flash Player NPAPI or PPAPI entry.
    Affected if The installed version is 11.2.202.460 or earlier, 13.0.0.289 or earlier, or any of these exact 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, 15.0.0.246, or any 14.x or 15.x version before 18.0.0.160.
  2. Check Adobe Flash Player version on Linux
    Open a terminal and run 'rpm -q flash-plugin' for RPM-based distributions, or check the browser plugin information through the browser's add-ons manager. The version is typically displayed in the plugin details.
    Affected if The installed version is 11.2.202.460 or earlier, or 11.2.202.466 or earlier.
  3. Check Adobe AIR version on Windows or macOS
    Open the Windows Control Panel or macOS Applications folder and look for Adobe AIR. Alternatively, launch the Adobe AIR Application Installer from the Start Menu or Applications folder, and the version is displayed in the title bar or about dialog.
    Affected if The installed version is 17.0.0.172 or earlier, or 17.0.0.144 or earlier.
  4. Check Adobe AIR SDK version
    Navigate to the AIR SDK installation directory and locate the version file, or check the AIR SDK version through your development IDE if integrated. The version is typically visible in the SDK release notes or in a version.txt file within the SDK folder.
    Affected if The installed AIR SDK version is 17.0.0.172 or earlier.
  5. Check for Adobe Flash on Google Android
    Open the Google Play Store app, search for Adobe Flash Player, and check if it is installed on the device. Alternatively, check the device settings under Apps or Application Manager for any Adobe Flash Player entry.
    Affected if Adobe Flash Player is installed on any version of Google Android, as all versions are affected.

The environment is affected if Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe Flash Player for Android is installed and the version matches any of the vulnerable versions listed in the affected products and versions.

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 13.0.0.292/18.0.0.160 or later and Adobe AIR to 18.0.0.144/18.0.0.143 or later. Since Flash Player is end-of-life, consider removing it entirely if not required.

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); AIR 18.0.0.144 (Windows) / 18.0.0.143 (OS X/Android)

  1. Identify the exact installed version of Adobe Flash Player, Adobe AIR, or Adobe AIR SDK in your environment
  2. Consult the Adobe Security Bulletin APSB15-11 (https://helpx.adobe.com/security/products/flash-player/apsb15-11.html) for the appropriate fixed version for your platform
  3. For Flash Player 13.x: upgrade to version 13.0.0.292 or later
  4. For Flash Player 14.x-18.x: upgrade to version 18.0.0.160 or later
  5. For Flash Player on Linux: upgrade to version 11.2.202.466 or later
  6. For Adobe AIR (Windows): upgrade to version 18.0.0.144 or later
  7. For Adobe AIR (OS X/Android): upgrade to version 18.0.0.143 or later
  8. For Adobe AIR SDK (Windows): upgrade to version 18.0.0.144 or later
Caveat Adobe Flash Player reached end-of-life on December 31, 2020 and should be removed/uninstalled rather than upgraded; if AIR SDK is required, ensure compatibility with your build environment

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
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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