CVE-2017-11368 In MIT Kerberos 5 (aka krb5) 1.7 and later, an authenticated attacker can cause a KDC assertion failure by sending invalid S4U2Self or S4U2Proxy requests.
MediumCVSS 6.5
EPSS 2.4%
- Published
- Updated
- Exploit status
- No public exploit known
Description
In MIT Kerberos 5 (aka krb5) 1.7 and later, an authenticated attacker can cause a KDC assertion failure by sending invalid S4U2Self or S4U2Proxy requests.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/krb5(Debian:12) | < 1.15.1-2 | 1.15.1-2 |
| debian/krb5(Debian:13) | < 1.15.1-2 | 1.15.1-2 |
| debian/krb5(Debian:14) | < 1.15.1-2 | 1.15.1-2 |
| fedoraproject fedora | = 25 | No fix listed |
| fedoraproject fedora | = 26 | No fix listed |
| mit kerberos | = 5-1.13.7 | No fix listed |
| mit kerberos 5 | = 1.7 | No fix listed |
| mit kerberos 5 | = 1.7.1 | No fix listed |
| mit kerberos 5 | = 1.8 | No fix listed |
| mit kerberos 5 | = 1.8.1 | No fix listed |
| mit kerberos 5 | = 1.8.2 | No fix listed |
| mit kerberos 5 | = 1.8.3 | No fix listed |
| mit kerberos 5 | = 1.8.4 | No fix listed |
| mit kerberos 5 | = 1.8.5 | No fix listed |
| mit kerberos 5 | = 1.8.6 | No fix listed |
| mit kerberos 5 | = 1.9 | No fix listed |
| mit kerberos 5 | = 1.9.1 | No fix listed |
| mit kerberos 5 | = 1.9.2 | No fix listed |
| mit kerberos 5 | = 1.9.3 | No fix listed |
| mit kerberos 5 | = 1.9.4 | No fix listed |
| mit kerberos 5 | = 1.10 | No fix listed |
| mit kerberos 5 | = 1.10.1 | No fix listed |
| mit kerberos 5 | = 1.10.2 | No fix listed |
| mit kerberos 5 | = 1.10.3 | No fix listed |
| mit kerberos 5 | = 1.10.4 | No fix listed |
Show 29 more
| Product | Affected versions | Fixed in |
|---|---|---|
| mit kerberos 5 | = 1.11 | No fix listed |
| mit kerberos 5 | = 1.11.1 | No fix listed |
| mit kerberos 5 | = 1.11.2 | No fix listed |
| mit kerberos 5 | = 1.11.3 | No fix listed |
| mit kerberos 5 | = 1.11.4 | No fix listed |
| mit kerberos 5 | = 1.11.5 | No fix listed |
| mit kerberos 5 | = 1.12 | No fix listed |
| mit kerberos 5 | = 1.12.1 | No fix listed |
| mit kerberos 5 | = 1.12.2 | No fix listed |
| mit kerberos 5 | = 1.12.3 | No fix listed |
| mit kerberos 5 | = 1.13 | No fix listed |
| mit kerberos 5 | = 1.13.1 | No fix listed |
| mit kerberos 5 | = 1.13.2 | No fix listed |
| mit kerberos 5 | = 1.13.3 | No fix listed |
| mit kerberos 5 | = 1.13.5 | No fix listed |
| mit kerberos 5 | = 1.13.6 | No fix listed |
| mit kerberos 5 | = 1.14 | No fix listed |
| mit kerberos 5 | = 1.14-alpha1 | No fix listed |
| mit kerberos 5 | = 1.14-beta1 | No fix listed |
| mit kerberos 5 | = 1.14-beta2 | No fix listed |
| mit kerberos 5 | = 1.14.1 | No fix listed |
| mit kerberos 5 | = 1.14.2 | No fix listed |
| mit kerberos 5 | = 1.14.3 | No fix listed |
| mit kerberos 5 | = 1.14.4 | No fix listed |
| mit kerberos 5 | = 1.14.5 | No fix listed |
| mit kerberos 5 | = 1.15 | No fix listed |
| mit kerberos 5 | = 1.15.1 | No fix listed |
| mit kerberos 5 | = 1.15.1-beta1 | No fix listed |
| mit kerberos 5 | = 1.15.1-beta2 | No fix listed |
References
- Debian Security Tracker CVE-2017-11368 vendor-advisory
- 100291 third-party-advisory vdb-entry
- RHSA-2018:0666 vendor-advisory
- github.com patch third-party-advisory
- FEDORA-2017-e5b36383f4 vendor-advisory
- FEDORA-2017-8e9d9771c4 vendor-advisory
- bugs.debian.org issue-tracking