CVE-2020-36167: Malicious File Upload

Published Jan 6, 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.

Affected Software

2 affected components
Veritas Backup Exec>=20.0<20.0.1188.2734
Veritas Backup Exec>=21.0<21.0.1200.1217

Event History

Jan 6, 2021
CVE Published
via MITRE·12:51 AM
Data Sourced
via MITRE·12:51 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-36167?

CVE-2020-36167 is classified as a medium severity vulnerability.

2

How do I fix CVE-2020-36167?

To fix CVE-2020-36167, apply hotfix 298543 for versions 20.6 and earlier or hotfix 657517 for version 21.1.

3

Which versions of Veritas Backup Exec are affected by CVE-2020-36167?

CVE-2020-36167 affects Veritas Backup Exec versions 16.2, 20.6 before hotfix 298543, and 21.1 before hotfix 657517.

4

What is the main issue described in CVE-2020-36167?

The main issue in CVE-2020-36167 is the loading of an insecure OpenSSL library configuration file during the start-up of the server.

5

Is there a workaround for CVE-2020-36167?

Currently, the recommended approach is to apply the appropriate hotfix rather than relying on a workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203