dbcve.org
AirApplication · Adobe

CVE-2015-3087

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
High EPSS 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
Integer overflow in 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 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 · moderate confidence

Integer overflow vulnerability in Adobe Flash Player and Adobe AIR that allows remote attackers to execute arbitrary code via unspecified vectors. The overflow occurs during memory allocation calculations, potentially enabling attackers to corrupt memory and achieve code execution.

MitigationUpdate Adobe Flash Player to version 13.0.0.289 (Windows/OS X) or 11.2.202.460 (Linux), or version 17.0.0.188 for 14.x-17.x. For Adobe AIR, update to 17.0.0.172. Alternatively, remove or disable Flash Player if no longer 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. Detect Adobe Flash Player version on Windows
    Open Registry Editor (regedit.exe), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or for 64-bit systems also check HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\CurrentVersion. Read the 'Version' value.
    Affected if The version number is less than or equal to 11.2.202.475; less than or equal to 13.0.0.264; equals 14.0.0.125, 14.0.0.145, 14.0.0.176, or 14.0.0.179; equals 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; or is any version 16.x or 17.x up to and including 17.0.0.172.
  2. Detect Adobe Flash Player version on macOS
    Open Terminal and run: defaults read /Library/Application\ Support/Adobe/Flash\ Player/installedLocations or check /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info.plist for CFBundleVersion.
    Affected if The version number matches any of the affected Flash Player versions listed above.
  3. Detect Adobe AIR version on Windows
    Open Registry Editor (regedit.exe), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\Versions, or check the version in Add/Remove Programs. The version is also visible in the executable properties of the AIR application.
    Affected if The Adobe AIR version is 17.0.0.144 or earlier.
  4. Detect Adobe AIR version on macOS
    Open Terminal and run: defaults read /Library/Preferences/com.adobe.air.version or check /Applications/Adobe AIR Installer/Contents/Info.plist for the version.
    Affected if The Adobe AIR version is 17.0.0.144 or earlier.
  5. Check for presence of vulnerable Flash or AIR components
    On Windows, search for flash*.ocx or Flash*.dll in C:\Windows\System32\Macromed\Flash. On macOS, check /Library/Application Support/Adobe/Flash Player or /Library/Internet Plug-Ins/Flash Player.plugin.
    Affected if Any Flash or AIR component with a version matching the affected ranges above is found on the system.

The environment is affected if Adobe Flash Player or Adobe AIR is installed with any version listed in the affected ranges for this 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 17.0.0.144
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.289 (Windows/OS X) or 11.2.202.460 (Linux), or version 17.0.0.188 for 14.x-17.x. For Adobe AIR, update to 17.0.0.172. Alternatively, remove or disable Flash Player if no longer required.

Recommended fix High confidence

Adobe Flash Player 17.0.0.188+ (Windows/OS X), 13.0.0.289+ (Flash 13.x), 11.2.202.460+ (Linux); Adobe AIR 17.0.0.172+

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system plugin list
  2. 2. Identify the installed Adobe AIR version from the AIR Application Installer or system programs list
  3. 3. For Flash Player on Windows/OS X: upgrade to version 17.0.0.188 or later (or 13.0.0.289 for Flash 13.x)
  4. 4. For Flash Player on Linux: upgrade to version 11.2.202.460 or later
  5. 5. For Adobe AIR: upgrade to version 17.0.0.172 or later
  6. 6. For Adobe AIR SDK: upgrade to version 17.0.0.172 or later
  7. 7. Verify the updated versions are installed and the vulnerability is patched
  8. 8. Consider removing Flash Player if no longer needed, as Adobe ended support in December 2020
Caveat Adobe Flash Player reached end-of-life in December 2020 and no longer receives security updates; 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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