dbcve.org
AirApplication · Adobe

CVE-2015-6676

HIGH · 10.0 CVSS v2.0 Published 2015-09-22
Fix available
A fix is available. Upgrade to after 18.0.0.199 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
Buffer overflow in Adobe Flash Player before 18.0.0.241 and 19.x before 19.0.0.185 on Windows and OS X and before 11.2.202.521 on Linux, Adobe AIR before 19.0.0.190, Adobe AIR SDK before 19.0.0.190, and Adobe AIR SDK & Compiler before 19.0.0.190 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-6678.

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

Buffer overflow vulnerability in Adobe Flash Player and Adobe AIR that allows attackers to execute arbitrary code via unspecified vectors. The vulnerability affects multiple software versions across Windows, OS X, and Linux platforms.

MitigationUpdate Adobe Flash Player to version 18.0.0.241/19.0.0.185 or later, Adobe AIR to 19.0.0.190 or later, and corresponding AIR SDK versions. Given the CVSS 10 severity and arbitrary code execution capability, prioritized patching is critical.

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.199<= 18.0.0.143
Air SdkApplication
Affected:<= 18.0.0.199
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.180
Flash PlayerApplication
Affected:<= 11.2.202.508<= 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
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 any Flash-enabled content in a browser, right-click and select 'About Adobe Flash Player', or check the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion
    Affected if The displayed version is 11.2.202.508 or earlier, 13.0.0.289 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, 15.0.0.246
  2. Check Adobe Flash Player version on macOS
    Open any Flash-enabled content in a browser, right-click and select 'About Adobe Flash Player', or check /Library/Application Support/Macromedia/FlashPlayerTrustedURLs.xml
    Affected if The displayed version matches any of the affected versions listed above
  3. Check Adobe AIR version on Windows or macOS
    On Windows, open the command prompt and run: C:\Program Files\Adobe\Adobe AIR\Version.exe -version (path may vary). On macOS, run: /Applications/Adobe AIR/Versions/1.0/Adobe AIR Application Installer -version in Terminal
    Affected if The reported version is 18.0.0.199 or earlier, or 18.0.0.143 or earlier
  4. Check Adobe AIR SDK version
    Look for the AIR SDK version file or check the SDK release notes in the installed directory, or run: adt -version if AIR Developer Tool is available
    Affected if The SDK version is 18.0.0.199 or earlier (AIR SDK), or 18.0.0.180 or earlier (AIR SDK & Compiler)
  5. Check if running on Android with Flash Player
    On the Android device, go to Settings > Apps > Adobe Flash Player (or check installed apps list), or run: getprop ro.build.version.release and check for any Flash Player APK installed
    Affected if Adobe Flash Player for Android is installed on any Android version

You are affected if Flash Player, AIR, or AIR SDK matches any of the specific version numbers in the affected ranges, or if Flash Player is installed on any Android device.

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

Update Adobe Flash Player to version 18.0.0.241/19.0.0.185 or later, Adobe AIR to 19.0.0.190 or later, and corresponding AIR SDK versions. Given the CVSS 10 severity and arbitrary code execution capability, prioritized patching is critical.

Recommended fix High confidence

Flash Player 18.0.0.241+/19.0.0.185+ (Win/OSX), 11.2.202.521+ (Linux); AIR 19.0.0.190+; AIR SDK 19.0.0.190+

  1. Identify the exact Adobe Flash Player, AIR, AIR SDK, or AIR SDK & Compiler version currently installed
  2. For Flash Player on Windows/OS X: upgrade to version 18.0.0.241 or 19.0.0.185 or later
  3. For Flash Player on Linux: upgrade to version 11.2.202.521 or later
  4. For Adobe AIR: upgrade to version 19.0.0.190 or later
  5. For Adobe AIR SDK: upgrade to version 19.0.0.190 or later
  6. For Adobe AIR SDK & Compiler: upgrade to version 19.0.0.190 or later
  7. For Android: uninstall Flash Player plugin/browser integration as no patch is available
  8. Restart any affected browsers or applications after upgrade
Caveat Adobe Flash Player and AIR reached end-of-life on December 31, 2020; upgrade may not be possible for deprecated products

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