CVE-2018-16860
CVE-2018-16860 Vulnerability Analysis & Exploit Intelligence
A flaw was found in samba's Heimdal KDC implementation, versions 4.8.x up to, excluding 4.8.12, 4.9.x up to, excluding 4.9.8 and 4.10.x up to, excluding 4.10.3, when used in AD DC mode. A man in the middle attacker could use this flaw to intercept the request to the KDC and replace the user name (principal) in the request with any desired user name (principal) that exists in the KDC effectively obtaining a ticket for that principal.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
2%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-358
References
17 on the record
- www.synology.com/security/advisory/Synology_SA_19_23
x_refsource_CONFIRM
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16860
x_refsource_CONFIRM
- www.samba.org/samba/security/CVE-2018-16860.html
x_refsource_MISC
- seclists.org/bugtraq/2019/Aug/25
mailing-list, x_refsource_BUGTRAQ
- seclists.org/bugtraq/2019/Aug/22
mailing-list, x_refsource_BUGTRAQ
- seclists.org/bugtraq/2019/Aug/23
mailing-list, x_refsource_BUGTRAQ
- seclists.org/bugtraq/2019/Aug/21
mailing-list, x_refsource_BUGTRAQ
- lists.opensuse.org/opensuse-security-announce/2019-08/msg00026.html
vendor-advisory, x_refsource_SUSE
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.