krb5: Invalid S4U2Self or S4U2Proxy request causes assertion failure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | |||
| krb5-0:1.15.1-18.el7 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2018:0666 | 2018-04-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1058-1 | krb5 security update |
EUVD |
EUVD-2017-2995 | 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. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 2.4% (2.397% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.