First published: Wed Jan 06 2021(Updated: )
An issue was discovered in the server in Veritas Backup Exec through 16.2, 20.6 before hotfix 298543, and 21.1 before hotfix 657517. On start-up, it loads the OpenSSL library from the Installation folder. This library in turn 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. A low privileged user can create a :\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. If the system is also an Active Directory domain controller, then this can affect the entire domain.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Veritas Backup Exec | >=20.0<20.0.1188.2734 | |
Veritas Backup Exec | >=21.0<21.0.1200.1217 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-36167 is classified as a medium severity vulnerability.
To fix CVE-2020-36167, apply hotfix 298543 for versions 20.6 and earlier or hotfix 657517 for version 21.1.
CVE-2020-36167 affects Veritas Backup Exec versions 16.2, 20.6 before hotfix 298543, and 21.1 before hotfix 657517.
The main issue in CVE-2020-36167 is the loading of an insecure OpenSSL library configuration file during the start-up of the server.
Currently, the recommended approach is to apply the appropriate hotfix rather than relying on a workaround.