PatchTheCVEunitrends vulnerabilities
Recent CVEs affecting unitrends products. 8 tracked.
unitrends has 8 tracked vulnerabilities, 4 critical. A fixed release or vendor patch exists for 8. Most recent: 2020-02-17. Highest priority: CVE-2018-6329 (score 69/100).
- CVE-2020-8427 CRITICAL 9.8 UPGRADE In Unitrends Backup before 10.4.1, an HTTP request parameter was not properly sanitized, allowing for SQL inje
- CVE-2018-6329 CRITICAL 9.8 UPGRADE It was discovered that the Unitrends Backup (UB) before 10.1.0 libbpext.so authentication could be bypassed wi
- CVE-2017-7284 HIGH 8.8 UPGRADE An attacker that has hijacked a Unitrends Enterprise Backup (before 9.1.2) web server session can leverage api
- CVE-2017-7283 HIGH 8.8 UPGRADE An authenticated user of Unitrends Enterprise Backup before 9.1.2 can execute arbitrary OS commands by sending
- CVE-2017-7282 MEDIUM 5.5 UPGRADE An issue was discovered in Unitrends Enterprise Backup before 9.1.1
- CVE-2017-7281 HIGH 8.8 UPGRADE An issue was discovered in Unitrends Enterprise Backup before 9.1.2
- CVE-2017-7280 CRITICAL 9.8 UPGRADE An issue was discovered in api/includes/systems.php in Unitrends Enterprise Backup before 9.0.0
- CVE-2017-7279 CRITICAL 9.8 UPGRADE An unprivileged user of the Unitrends Enterprise Backup before 9.0.0 web server can escalate to root privilege
FAQ
How do I fix unitrends vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is unitrends being exploited right now?
None of the tracked unitrends CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which unitrends CVE should I patch first?
CVE-2018-6329 currently ranks highest (69/100): It was discovered that the Unitrends Backup (UB) before 10.1.0 libbpext.so authentication could be bypassed wi.