CVE-2017-15548
No exploitation reported by the sources we read.
- Published2018-01-05
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An issue was discovered in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0; EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x; and EMC Integrated Data Protection Appliance 2.0. A remote unauthenticated malicious user can potentially bypass application authentication and gain unauthorized root access to the affected systems.
Timeline
dates in UTC- 2018-01-0517:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-15548?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-15548?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.1 | = 7.1-21 | no fix published | NVD |
| 7.1 | = 7.1-145 | no fix published | NVD |
| 7.1 | = 7.1-302 | no fix published | NVD |
| 7.1 | = 7.1-370 | no fix published | NVD |
| 7.2 | = 7.2-32 | no fix published | NVD |
| 7.2 | = 7.2-309 | no fix published | NVD |
| 7.2 | = 7.2-401 | no fix published | NVD |
| 7.3 | = 7.3-125 | no fix published | NVD |
| 7.3 | = 7.3-211 | no fix published | NVD |
| 7.3 | = 7.3-226 | no fix published | NVD |
| 7.3 | = 7.3-233 | no fix published | NVD |
| 7.4 | = 7.4-58 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.0 | = 9.0 | no fix published | NVD |
| 9.1 | = 9.1 | no fix published | NVD |
| 9.2 | = 9.2 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | = 2.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- NVDweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score4.7 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-01-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-15548?
Is CVE-2017-15548 actively exploited?
What is the CVSS score for CVE-2017-15548?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.