CVE-2017-11368Published Aug 9, 2017 · Aug 9Updated Oct 24
In MIT Kerberos 5 (aka krb5) 1.7 and later, an authenticated attacker can cause a KDC assertion failure by sending in…
Medium6.5Fix available
MIT Kerberos 5 (krb5) 1.7 and later is vulnerable to a KDC assertion failure. An authenticated attacker can trigger it by sending invalid S4U2Self or S4U2Proxy requests.
Administrators running MIT Kerberos 5 (krb5) 1.7 or later should check their KDCs.