CVE-2020-36168: Critical severity veritas resiliency platform vulnerability
An issue was discovered in Veritas Resiliency Platform 3.4 and 3.5. It leverages OpenSSL on Windows systems when using the Managed Host addon. On start-up, it loads the OpenSSL library. This library may attempt to load the openssl.cnf configuration file, which does not exist. By default, on Windows systems, users can create directories under C:\. A low privileged user can create a C:\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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-36168?
CVE-2020-36168 is classified as a high severity vulnerability due to potential security implications in Veritas Resiliency Platform.
How do I fix CVE-2020-36168?
To mitigate CVE-2020-36168, ensure that the OpenSSL library is properly configured and the necessary configuration files are in place before startup.
What software versions are affected by CVE-2020-36168?
CVE-2020-36168 affects Veritas Resiliency Platform versions 3.4 and 3.5.
What kind of systems are impacted by CVE-2020-36168?
CVE-2020-36168 impacts Windows systems using the Managed Host addon of the Veritas Resiliency Platform.
Is there a workaround for CVE-2020-36168?
A potential workaround for CVE-2020-36168 includes creating a dummy openssl.cnf configuration file to avoid the library load issue.