dbcve.org
AirApplication · Adobe

CVE-2015-3117

HIGH · 10.0 CVSS v2.0 Published 2015-07-09
Fix available
A fix is available. Upgrade to after 18.0.0.144 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
Adobe Flash Player before 13.0.0.302 and 14.x through 18.x before 18.0.0.203 on Windows and OS X and before 11.2.202.481 on Linux, Adobe AIR before 18.0.0.180, Adobe AIR SDK before 18.0.0.180, and Adobe AIR SDK & Compiler before 18.0.0.180 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3123, CVE-2015-3130, CVE-2015-3133, CVE-2015-3134, and CVE-2015-4431.

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 or cause denial of service via unspecified vectors. Affects Flash Player versions before 13.0.0.302 and 14.x-18.x before 18.0.0.203 on Windows/OS X, and before 11.2.202.481 on Linux, as well as AIR versions before 18.0.0.180.

MitigationUpgrade Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or later (11.2.202.481 or later on Linux), and Adobe AIR to 18.0.0.180 or later. Consider removing Flash Player 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
AirApplication
Affected:<= 18.0.0.144
Air SdkApplication
Affected:<= 18.0.0.144
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.144
Flash PlayerApplication
Affected:<= 11.2.202.468<= 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

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 installed Flash Player version in browsers
    Open browser plugin settings or visit 'about:plugins' (Firefox) or chrome://plugins (Chrome) to list the Flash Player plugin version, or check the file properties of npctrl.dll (NPAPI) or pepflashplayer.dll (PPAPI) in the browser's plugin directories
    Affected if The displayed version is 11.2.202.468 or earlier, 13.0.0.289 or earlier, 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. Check standalone Flash Player installation on Windows
    Locate the Flash Player installation directory (commonly in System32 or Program Files) and view the version property of flash32_XXX.ocx or flash64_XXX.ocx, or check Add/Remove Programs for the Adobe Flash Player entry
    Affected if The installed version matches any of the affected Flash Player versions listed in the CVE
  3. Check Adobe AIR version on Windows or macOS
    Open the Adobe AIR application list (on Windows: Check the version in Add/Remove Programs; on macOS: Check /Applications/Adobe AIR folder or the application's info.plist), or locate air.swf or the AIR runtime in the installation directory and check its file version
    Affected if The AIR version is 18.0.0.144 or earlier (the fixed version is 18.0.0.180)
  4. Verify Adobe AIR SDK or AIR SDK & Compiler installation
    If the AIR SDK is installed for development, check the version file or manifest within the SDK directory (typically named version.properties or found in the SDK's root), or run 'adl -version' from the SDK bin directory if available
    Affected if The SDK version is 18.0.0.144 or earlier

The environment is affected if any installed Adobe Flash Player or Adobe AIR version falls within the vulnerable version ranges specified in the CVE.

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

Upgrade Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or later (11.2.202.481 or later on Linux), and Adobe AIR to 18.0.0.180 or later. Consider removing Flash Player if unnecessary given its end-of-life status.

Recommended fix High confidence

Flash Player: 13.0.0.302+ (13.x branch), 18.0.0.203+ (14.x-18.x branch), 11.2.202.481+ (Linux); Adobe AIR/SDK: 18.0.0.180+

  1. 1. Identify the installed Adobe Flash Player version by navigating to https://helpx.adobe.com/flash-player.html or checking About Flash Player in the browser
  2. 2. Identify the installed Adobe AIR version from Control Panel (Windows) or Applications folder (Mac)
  3. 3. For Flash Player on Windows or OS X: If using version 13.x, upgrade to 13.0.0.302 or later; if using version 14.x-18.x, upgrade to 18.0.0.203 or later
  4. 4. For Flash Player on Linux: Upgrade to version 11.2.202.481 or later
  5. 5. For Adobe AIR desktop runtime: Upgrade to version 18.0.0.180 or later
  6. 6. For Adobe AIR SDK: Upgrade to version 18.0.0.180 or later
  7. 7. For Adobe AIR SDK & Compiler: Upgrade to version 18.0.0.180 or later
  8. 8. Clear browser cache and restart browsers after upgrading
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating to HTML5 alternatives as no further updates are available

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

Fix this in Air Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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