Flash PlayerApplication · Adobe

CVE-2015-7637

HIGH · 10.0 CVSS v2.0 Published 2015-10-18
Fix available
A fix is available. Upgrade to after 19.0.0.190 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.252 and 19.x before 19.0.0.207 on Windows and OS X and before 11.2.202.535 on Linux, Adobe AIR before 19.0.0.213, Adobe AIR SDK before 19.0.0.213, and Adobe AIR SDK & Compiler before 19.0.0.213 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-7629, CVE-2015-7631, CVE-2015-7635, CVE-2015-7636, CVE-2015-7638, CVE-2015-7639, CVE-2015-7640, CVE-2015-7641, CVE-2015-7642, CVE-2015-7643, and CVE-2015-7644.

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 memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. The vulnerability exists in unspecified vectors within the affected Flash Player versions (pre-18.0.0.252/19.0.0.207 on Windows/OS X, pre-11.2.202.535 on Linux) and AIR products (pre-19.0.0.213).

MitigationUpgrade Adobe Flash Player to version 18.0.0.252 or 19.0.0.207+ (or 11.2.202.535+ on Linux), and Adobe AIR to version 19.0.0.213+. Given Flash Player end-of-life, consider removing Flash entirely if unused.

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:<= 11.2.202.521<= 19.0.0.185
AirApplication
Affected:<= 19.0.0.190
Air SdkApplication
Affected:<= 19.0.0.190
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.190

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 Windows Control Panel > Programs and Features, look for Adobe Flash Player entry, or check browser plugin list (in Chrome type chrome://plugins, in Firefox add-ons > plugins). Alternatively, check file version of npppdf.dll or flash*.ocx in system directories.
    Affected if Installed version is 11.2.202.521 or lower, or 19.0.0.185 or lower (for 19.x branch)
  2. Check Adobe Flash Player version on macOS
    Open Finder > Go > Go to Folder > /Library/Internet Plug-Ins/ and check for Flash Player plugin file info, or check browser plugin list in Safari or Chrome.
    Affected if Installed version is 11.2.202.521 or lower, or 19.0.0.185 or lower (for 19.x branch)
  3. Check Adobe Flash Player version on Linux
    Check for installed Flash package via package manager (dpkg -l | grep flash or rpm -qa | grep flash) or check /usr/lib/flash-plugin/ directory for version file.
    Affected if Installed version is 11.2.202.521 or lower
  4. Check Adobe AIR version
    Open Windows Control Panel > Programs and Features and look for Adobe AIR entry, or on macOS check /Applications/Adobe AIR folder, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR on Windows.
    Affected if Installed version is 19.0.0.190 or lower
  5. Check Adobe AIR SDK version
    If using Adobe AIR SDK for development, check the AIR SDK version by locating the SDK directory and reading the readme or version file within it.
    Affected if Installed SDK version is 19.0.0.190 or lower

User is affected if Adobe Flash Player version is <= 11.2.202.521, <= 19.0.0.185, or Adobe AIR/SDK version is <= 19.0.0.190 on their system.

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

Upgrade Adobe Flash Player to version 18.0.0.252 or 19.0.0.207+ (or 11.2.202.535+ on Linux), and Adobe AIR to version 19.0.0.213+. Given Flash Player end-of-life, consider removing Flash entirely if unused.

Recommended fix High confidence

Flash Player 18.0.0.252/19.0.0.207/11.2.202.535 (Linux) and AIR 19.0.0.213 or later

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or checking Add/Remove Programs
  2. 2. Identify the currently installed Adobe AIR version via Add/Remove Programs or the AIR version checker
  3. 3. Download the fixed version from Adobe's official security bulletin APSB15-25: Flash Player 18.0.0.252 (or 19.0.0.207+ for branch 19), 11.2.202.535 for Linux; AIR 19.0.0.213 or later
  4. 4. Uninstall the current vulnerable Adobe Flash Player version via Control Panel > Programs and Features
  5. 5. Uninstall the current vulnerable Adobe AIR version via Control Panel > Programs and Features
  6. 6. Install the patched Flash Player version appropriate for your OS (Windows, OS X, or Linux)
  7. 7. Install the patched AIR SDK/SDK&Compiler version if applicable
  8. 8. Restart all browsers and applications that utilize Flash Player or AIR
Caveat Adobe Flash Player and AIR have reached end-of-life; consider migrating away from Flash-based content as Adobe ended support after December 2020

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

Fix this in Flash Player 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-7637 — 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-7637 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