dbcve.org
AirApplication · Adobe

CVE-2015-3093

HIGH · 10.0 CVSS v2.0 Published 2015-05-13
Fix available
A fix is available. Upgrade to after 17.0.0.144 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
Adobe Flash Player before 13.0.0.289 and 14.x through 17.x before 17.0.0.188 on Windows and OS X and before 11.2.202.460 on Linux, Adobe AIR before 17.0.0.172, Adobe AIR SDK before 17.0.0.172, and Adobe AIR SDK & Compiler before 17.0.0.172 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3078, CVE-2015-3089, and CVE-2015-3090.

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 · moderate 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. The vulnerability affects multiple versions across Windows, OS X, and Linux platforms.

MitigationUpgrade to Adobe Flash Player 13.0.0.289 / 17.0.0.188 / 11.2.202.460 (depending on version and platform) and Adobe AIR 17.0.0.172. Remove or disable Flash 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
AirApplication
Affected:<= 17.0.0.144
Air SdkApplication
Affected:<= 17.0.0.144
Air Sdk \& CompilerApplication
Affected:<= 17.0.0.144
Flash PlayerApplication
Affected:<= 11.2.202.475<= 13.0.0.264= 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. Check Adobe Flash Player version on Windows
    Open Control Panel > Programs and Features, look for Adobe Flash Player in the list, or visit the Adobe version check page at about:flash in a browser, or check the file version of npapi_flash.dll in C:\Windows\System32\Macromed\Flash\
    Affected if The installed version is 11.2.202.475 or earlier, 13.0.0.264 or earlier, or matches any of these: 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 Adobe Flash Player version on OS X
    Open Finder > Applications > Utilities > Adobe Flash Player, or check the file version of /Library/Internet Plug-Ins/Flash Player.plugin, or visit the Adobe version check page in a browser
    Affected if The installed version is 11.2.202.475 or earlier, 13.0.0.264 or earlier, or matches any of the specific 14.x or 15.x versions listed in the affected versions
  3. Check Adobe Flash Player version on Linux
    Check the package version via dpkg -l | grep flash or rpm -q flash-plugin, or examine the version of libflashplayer.so in /usr/lib/flash-plugin/ or /usr/lib/mozilla/plugins/
    Affected if The installed version is 11.2.202.475 or earlier on Linux
  4. Check Adobe AIR version
    Open Control Panel > Programs and Features on Windows, or check the file version of AIR*.dll in the Adobe AIR installation directory, or run 'air -version' from command line if AIR SDK is installed
    Affected if The installed Adobe AIR version is 17.0.0.144 or earlier (including Adobe Air Sdk and Adobe Air Sdk & Compiler)
  5. Verify if Flash Player plugin is enabled in browsers
    Open browser add-ons or extensions manager (chrome://extensions in Chrome, about:addons in Firefox) and check if the Flash Player plugin is active or set to 'Always Activate'
    Affected if Flash Player plugin is enabled and the browser can render SWF content, which is required to trigger the vulnerability through malicious flash content

You are affected if Adobe Flash Player is installed at any of the vulnerable versions listed (including specific 14.x and 15.x versions or any version at or below 11.2.202.475, 13.0.0.264, or 17.0.0.144 for AIR) and the Flash plugin is active in a browser or application that can process SWF files.

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

Upgrade to Adobe Flash Player 13.0.0.289 / 17.0.0.188 / 11.2.202.460 (depending on version and platform) and Adobe AIR 17.0.0.172. Remove or disable Flash if not required.

Recommended fix High confidence

Flash Player 17.0.0.188+ (14-17.x), 13.0.0.289+ (13.x), 11.2.202.460+ (Linux); AIR 17.0.0.172+

  1. Identify the installed Adobe Flash Player version via About or system utilities
  2. For Windows/OS X Flash Player 14.x-17.x: Upgrade to version 17.0.0.188 or later
  3. For Windows/OS X Flash Player 13.x: Upgrade to version 13.0.0.289 or later
  4. For Linux Flash Player: Upgrade to version 11.2.202.460 or later
  5. For Adobe AIR, AIR SDK, or AIR SDK & Compiler: Upgrade to version 17.0.0.172 or later
  6. Verify the installed version matches or exceeds the fixed version for your product line
  7. Restart any browsers or applications using Flash Player after the update
Caveat Adobe Flash Player is deprecated and no longer supported; consider migrating away from Flash-based content

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-3093 — 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-3093 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