CVE-2020-6014 Vulnerability Analysis & Exploit Details

CVE-2020-6014
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2020-6014 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2020-6014 Details

Status: Analyzed

Last updated: 🕞 19 Nov 2020, 15:55 UTC
Originally published on: 🕘 02 Nov 2020, 21:15 UTC

Time between publication and last update: 16 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2020-6014 Vulnerability Summary

CVE-2020-6014: 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.

Assessing the Risk of CVE-2020-6014

Access Complexity Graph

The exploitability of CVE-2020-6014 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2020-6014

The exploitability of CVE-2020-6014 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2020-6014, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2020-6014, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2020-6014 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2020-6014 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2020-6014 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.044% (probability of exploit)

EPSS Percentile: 15.33% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 84.67% of others.

CVE-2020-6014 References

External References

CWE Common Weakness Enumeration

CWE-114

CAPEC Common Attack Pattern Enumeration and Classification

  • Command Line Execution through SQL Injection CAPEC-108 An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Inclusion of Code in Existing Process CAPEC-640 The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, function hooking, reflective code loading, and more.

Vulnerable Configurations

  • cpe:2.3:a:checkpoint:endpoint_security:e80:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e83:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e83:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e84:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e84:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e85:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e85:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e86:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e86:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:r73:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:r73:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.10:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.10:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.20:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.20:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.30:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.30:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.40:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.40:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.41:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.41:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.50:-:vpn_blade:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.50:-:vpn_blade:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.64:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.64:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.65:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.65:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.70:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.70:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.71:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.71:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.72:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.72:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.80:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.80:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.81:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.81:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.82:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.82:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.82.1:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.82.1:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.83:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.83:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.84:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.84:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.85:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.85:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.86:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.86:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.87:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.87:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.88:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.88:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.89:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.89:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.90:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.90:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.92:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.92:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.94:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.94:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.95:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.95:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.96:*:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.96:*:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e80.96:*:*:*:*:windows:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e80.96:*:*:*:*:windows:*:*
  • cpe:2.3:a:checkpoint:endpoint_security:e81.30:*:*:*:*:windows:*:*
    cpe:2.3:a:checkpoint:endpoint_security:e81.30:*:*:*:*:windows:*:*

Protect Your Infrastructure against CVE-2020-6014: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...