CVE-2017-8895 in the critical feed json
In Veritas Backup Exec 2014 before build 14.1.1187.1126, 15 before build 14.2.1180.3160, and 16 before FP1, there is a use-after-free vulne…
published 2017-05-10 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17835
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 71.0%
- EPSS 71.0% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
In Veritas Backup Exec 2014 before build 14.1.1187.1126, 15 before build 14.2.1180.3160, and 16 before FP1, there is a use-after-free vulnerability in multiple agents that can lead to a denial of service or remote code execution. An unauthenticated attacker can use this vulnerability to crash the agent or potentially take control of the agent process and then the system it is running on.
Patch / fix
- veritas backup_exec 14.1.1786.1126, 14.2.1180.3160, 16.0.1142.1327
Timeline
- First public exploit (Metasploit exploit/windows/backupexec/ssl_uaf)
- Published
Exploit prediction
71.00% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/backupexec/ssl_uaf Veritas/Symantec Backup Exec SSL NDMP Connection Use-After-Free metasploit exploit, normal rank, 2017-05-10
- EDB-42282 Veritas/Symantec Backup Exec - SSL NDMP Connection Use-After-Free (Metasploit) remote, 2017-06-29
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-416 Use After Free
References
-
veritas.com
/content/support/en_US/security/VTS17-006.html#Issue1
patch, vendor-advisory
-
exploit-db.com
/exploits/42282/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/98386
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038561
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8895
- NVD CVE-2017-8895
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.