Endpoint SecurityApplication · Checkpoint

CVE-2020-6014

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated

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
Check Point Endpoint Security Client for Windows, with Anti-Bot or Threat Emulation blades installed, before version E83.20, tries to load a non-existent DLL during a query for the Domain Name. An attacker with administrator privileges can leverage this to gain code execution within a Check Point Software Technologies signed binary, where under certain circumstances may cause the client to terminate.

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

This is a DLL planting/hijacking vulnerability in Check Point Endpoint Security Client for Windows (with Anti-Bot or Threat Emulation blades, versions before E83.20). The client attempts to load a non-existent DLL during domain name resolution queries. An attacker with administrator privileges can place a malicious DLL in the load path to achieve code execution within a Check Point-signed binary, which may also cause the client to crash.

MitigationUpgrade Check Point Endpoint Security Client for Windows to version E83.20 or later. Restrict administrator access to prevent unauthorized DLL planting.

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
Endpoint SecurityApplication
Affected:< e83.20

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 Check Point Endpoint Security Client installation and version
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\CheckPoint\Endpoint Security\, look for 'Check Point Endpoint Security' and note the installed version number
    Affected if The installed version is earlier than E83.20 (for example, E82.30, E81.00, etc.)
  2. Confirm Anti-Bot or Threat Emulation blade is enabled
    Open Check Point Endpoint Security Client GUI, navigate to the blades or components list, or check the Windows Services for 'Check Point Endpoint Security' related services. These blades add specific Threat Emulation or Anti-Bot components
    Affected if Either the Anti-Bot blade or Threat Emulation blade is listed as installed and active in the client configuration
  3. Identify the vulnerable DLL loading behavior during DNS queries
    Use Process Monitor (from Sysinternals) with a filter for the Check Point Endpoint Security client executable (commonly EndpointSecurity.exe or similar Check Point processes), then trigger domain name resolution (ping a hostname or use nslookup). Look for attempts to load a DLL that does not exist (NAME_NOT_FOUND)
    Affected if The client attempts to load a non-existent DLL from a writable path during DNS resolution operations, indicating the DLL hijacking vulnerability is present

You are affected if Check Point Endpoint Security Client for Windows with Anti-Bot or Threat Emulation blades is installed at a version earlier than E83.20, and the client exhibits DLL loading failures during domain resolution queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Check Point Endpoint Security Client for Windows to version E83.20 or later. Restrict administrator access to prevent unauthorized DLL planting.

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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