Flash PlayerApplication · Adobe

CVE-2015-6682

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
Use-after-free vulnerability 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-5570, CVE-2015-5574, CVE-2015-5581, and CVE-2015-5584.

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

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR allows attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from improper memory management where memory is accessed after being freed, enabling code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.241/19.0.0.185 or later (Windows/OS X), 11.2.202.521 or later (Linux), and Adobe AIR/SDK to 19.0.0.190 or later.

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:<= 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= 16.0.0.235
AirApplication
Affected:<= 18.0.0.143<= 18.0.0.199
AndroidOperating system
Affected:all versions
Air SdkApplication
Affected:<= 18.0.0.199
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.180

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 Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player, or right-click the Flash Player DLL (npflash32.dll or Flash64_18_0_0_241.dll) in C:\Windows\System32\Macromed\Flash and select Properties to view the File Version.
    Affected if The installed version matches any of these: 13.0.0.289 or earlier, 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, 16.0.0.235, or any version below 18.0.0.241 (Windows/OS X) or 11.2.202.521 (Linux).
  2. Check Adobe Flash Player version on Mac
    Open Terminal and run: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion, or navigate to /Library/Internet Plug-Ins/ and right-click Flash Player.plugin to view version info.
    Affected if The version matches any of the affected versions listed in the Windows check, or is earlier than 18.0.0.241 (OS X) or 11.2.202.521 (Linux).
  3. Check Adobe AIR runtime version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR, or check C:\Program Files\Adobe\Adobe AIR\Versions\1.0 folder for the AIR application files and view their version properties.
    Affected if The installed AIR version is 18.0.0.199 or earlier.
  4. Check Adobe AIR SDK version
    If using Adobe AIR for development, open the AIR SDK directory and locate the AIRSDKDescriptor.xml file, or check the version.txt file typically found in the SDK root folder.
    Affected if The AIR SDK version is 18.0.0.199 or earlier (SDK) or 18.0.0.180 or earlier (SDK & Compiler).
  5. Check for Flash Player plugin in web browsers
    In Chrome, type chrome://plugins in the address bar and look for Flash Player; in Firefox, type about:addons and select Plugins; in Internet Explorer, go to Manage Add-ons. Note the version displayed.
    Affected if The browser plugin version matches any of the affected Flash Player versions listed above.

A system is affected if Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Flash Player for Android is installed and the version falls within or below the affected ranges: Flash Player <=13.0.0.289 or any of the specific 14.x, 15.x, 16.x versions listed; AIR <=18.0.0.199; AIR SDK <=18.0.0.199; or any Android Flash Player version.

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 (Windows/OS X), 11.2.202.521 or later (Linux), and Adobe AIR/SDK to 19.0.0.190 or later.

Recommended fix High confidence

Flash Player 18.0.0.241 (Windows/OS X), 11.2.202.521 (Linux), or 19.0.0.185+ (19.x branch); Adobe AIR 19.0.0.190; Adobe AIR SDK 19.0.0.190; Adobe AIR SDK & Compiler 19.0.0.190

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the player's right-click menu or visiting the version check page
  2. 2. Identify the currently installed Adobe AIR version via Control Panel (Windows) or System Preferences (Mac)
  3. 3. For Flash Player on Windows/OS X: Download and install Flash Player 18.0.0.241 or later from the Adobe security bulletin
  4. 4. For Flash Player on Linux: Download and install version 11.2.202.521 or later
  5. 5. For Flash Player 19.x: Upgrade to version 19.0.0.185 or later
  6. 6. For Adobe AIR: Update to version 19.0.0.190 or later
  7. 7. For Adobe AIR SDK: Update to version 19.0.0.190 or later
  8. 8. For Adobe AIR SDK & Compiler: Update to version 19.0.0.190 or later
Caveat Adobe Flash Player is now deprecated and reached end-of-life on December 31, 2020; consider migrating to HTML5-based alternatives

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-6682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-6682 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