dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022. Known ransomware use
Enterprise Linux DesktopOperating system · Redhat

CVE-2015-7645

HIGH · 7.8 CVSS v3.1 Published 2015-10-15
Fix available
A fix is available. Upgrade to after 18.0.0.252 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit No privileges 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 18.x through 18.0.0.252 and 19.x through 19.0.0.207 on Windows and OS X and 11.x through 11.2.202.535 on Linux allows remote attackers to execute arbitrary code via a crafted SWF file, as exploited in the wild in October 2015.

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

Memory corruption vulnerability in Adobe Flash Player allowing remote code execution via crafted SWF files. Exploited in the wild in October 2015, affecting versions 18.x-18.0.0.252 and 19.x-19.0.0.207 on Windows/OS X, and 11.x-11.2.202.535 on Linux.

MitigationUpdate Adobe Flash Player to the latest version or remove/uninstall Flash Player if not required. In enterprise environments, deploy patches via patch management systems.

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
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 6.7
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server From RhuiOperating system
Affected:= 5.0= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0
Flash PlayerApplication
Affected:>= 18.0.0.160, <= 18.0.0.252= 19.0.0.185= 19.0.0.207<= 11.2.202.535
EvergreenOperating system
Affected:= 11.4
OpensuseOperating system
Affected:= 13.1= 13.2

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify Adobe Flash Player is installed
    Check for the presence of Flash Player NPAPI plugin. On Linux check /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/. On Windows check C:\Windows\System32\Macromed\Flash\ or browser plugin directories. On macOS check /Library/Internet\Plug-Ins/ or ~/Library/Internet\Plug-Ins/
    Affected if Adobe Flash Player is found installed on the system
  2. Retrieve installed Flash Player version on Windows
    Open the Windows Registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer or check the file version of NPSWF64.dll or NPSWF32.dll in the Flash installation directory
    Affected if The version string matches 18.0.0.160 through 18.0.0.252, equals 19.0.0.185, equals 19.0.0.207, or falls between 11.0.0.0 and 11.2.202.535 inclusive
  3. Retrieve installed Flash Player version on Linux
    Run rpm -q flash-plugin or check the version file at /usr/lib/flash-plugin/version.properties, or query dpkg for the flashplugin-installer package
    Affected if The version matches any of the affected Adobe Flash Player version ranges
  4. Check browser Flash plugin status
    In Firefox type about:plugins in the address bar, in Chrome navigate to chrome://plugins, or in Edge/IE check Manage Add-ons. Verify if the Flash Player plugin is enabled or simply present
    Affected if The Flash plugin is present and enabled in any web browser on the system
  5. Verify Red Hat or OpenSUSE system package versions
    On RHEL check rpm -qa | grep -i flash or yum list installed flash. On OpenSUSE run rpm -qa | grep -i flash-player. These distributions may ship Flash as part of their repositories
    Affected if The system has an affected Flash Player package installed from the distribution vendor

A user is affected if Adobe Flash Player versions 18.0.0.160-18.0.0.252, 19.0.0.185, 19.0.0.207, or 11.x up to 11.2.202.535 are installed and the browser plugin is enabled, regardless of operating 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 18.0.0.252
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to the latest version or remove/uninstall Flash Player if not required. In enterprise environments, deploy patches via patch management systems.

Recommended fix High confidence

Flash Player 20.0.0.228 or later (or 19.0.0.226 for the 19.x branch if staying on 19.x is required)

  1. 1. Identify the current Adobe Flash Player version installed (help > About Adobe Flash Player)
  2. 2. For Linux Enterprise systems (RHEL 5.x/6.x, CentOS, etc.), run 'yum update flash-plugin' or 'yum update nspluginwrapper' to apply vendor security updates
  3. 3. For openSUSE systems, run 'zypper patch' or 'zypper update flash-player' to install available security patches
  4. 4. Alternatively, navigate to https://get.adobe.com/flashplayer/ and download the latest version (20.0.0.228 or later) for your platform
  5. 5. After installation/update, restart all browsers and verify the new version via the Flash Player About page
  6. 6. If Flash Player is no longer needed, consider uninstalling it via the system package manager (yum remove flash-plugin or zypper remove flash-player)
Caveat Minimal risk for standard upgrades; however, some legacy content may require older Flash versions. Note: Adobe Flash Player reached end-of-life on December 31, 2020, and is no longer supported.

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

Fix this in Enterprise Linux Desktop Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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