CVE-2018-6329 in the critical feed json
It was discovered that the Unitrends Backup (UB) before 10.1.0 libbpext.so authentication could be bypassed with a SQL injection, allowing…
published 2018-03-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18090
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 61.2%
- EPSS 61.2% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
It was discovered that the Unitrends Backup (UB) before 10.1.0 libbpext.so authentication could be bypassed with a SQL injection, allowing a remote attacker to place a privilege escalation exploit on the target system and subsequently execute arbitrary commands.
Patch / fix
- unitrends backup 10.1.10
Timeline
- First public exploit (Metasploit exploit/linux/local/ueb_bpserverd_privesc)
- Published
Exploit prediction
61.24% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/local/ueb_bpserverd_privesc Unitrends Enterprise Backup bpserverd Privilege Escalation metasploit exploit, excellent rank, 2018-03-14
- EDB-45913 Unitrends Enterprise Backup - bpserverd Privilege Escalation (Metasploit) local, 2018-11-29
- EDB-44297 Unitrends UEB 10.0 - Root Remote Code Execution remote, 2018-03-16
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/44297/
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/45913/
exploit, third-party-advisory, vdb-entry
-
support.unitrends.com
/UnitrendsBackup/s/article/000006003
vendor-advisory
-
support.unitrends.com
/UnitrendsBackup/s/article/000001150
vendor-advisory
Sources
- CVE List CVE-2018-6329
- NVD CVE-2018-6329
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.