CVE-2020-36166 Vulnerability Analysis & Exploit Details

CVE-2020-36166
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2020-36166 an immediate threat requiring urgent mitigation.

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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2020-36166 Details

Status: Analyzed

Last updated: 🕖 12 Jan 2021, 19:22 UTC
Originally published on: 🕐 06 Jan 2021, 01:15 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2020-36166 Vulnerability Summary

CVE-2020-36166: An issue was discovered in Veritas InfoScale 7.x through 7.4.2 on Windows, Storage Foundation through 6.1 on Windows, Storage Foundation HA through 6.1 on Windows, and InfoScale Operations Manager (aka VIOM) Windows Management Server 7.x through 7.4.2. On start-up, it loads the OpenSSL library from \usr\local\ssl. This library attempts to load the \usr\local\ssl\openssl.cnf configuration file, which may not exist. On Windows systems, this path could translate to <drive>:\usr\local\ssl\openssl.cnf, where <drive> could be the default Windows installation drive such as C:\ or the drive where a Veritas product is installed. By default, on Windows systems, users can create directories under any top-level directory. A low privileged user can create a <drive>:\usr\local\ssl\openssl.cnf configuration file to load a malicious OpenSSL engine, resulting in arbitrary code execution as SYSTEM when the service starts. This gives the attacker administrator access on the system, allowing the attacker (by default) to access all data, access all installed applications, etc.

Assessing the Risk of CVE-2020-36166

Access Complexity Graph

The exploitability of CVE-2020-36166 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-36166

CVE-2020-36166 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-36166, 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-36166, 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-36166 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2020-36166 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2020-36166 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-36166 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:veritas:infoscale:7.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.2:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.3:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.300a:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.300a:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.101:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.101:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.103:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.103:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.400:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.400:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.500:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.0.0.500:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.100:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.100:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.200:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.200:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.300:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.300:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.400:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.400:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.500:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.500:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.600:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.600:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.700:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.700:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.800:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.1.0.800:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.2:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.100:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.100:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.200:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.200:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.300:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.2.0.300:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.100:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.100:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.200:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.200:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.300:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.0.300:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.100:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.100:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.200:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.200:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.300:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.300:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.400:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.400:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.500:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.500:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.600:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.600:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.700:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.700:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.800:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.3.1.800:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.100:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.100:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.200:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.200:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.300:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.300:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.400:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.400:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.500:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.500:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.600:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.600:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.700:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.700:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.800:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.800:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.900:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.0.900:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:infoscale_operations_manager:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:infoscale_operations_manager:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:storage_foundation:-:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:storage_foundation:-:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:storage_foundation:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:storage_foundation:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:storage_foundation_and_high_availability:-:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:storage_foundation_and_high_availability:-:*:*:*:*:*:*:*
  • cpe:2.3:a:veritas:storage_foundation_and_high_availability:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:veritas:storage_foundation_and_high_availability:6.1:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
    cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-36166: 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-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...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...