krb5: xdr_nullstring() doesn't check for terminating null character
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 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | |||
| krb5-0:1.10.3-42z1.el6_7 | cpe:/o:redhat:enterprise_linux:6 | RHSA-2016:0493 | 2016-03-22T00:00:00Z |
| Red Hat Enterprise Linux 7 | |||
| krb5-0:1.13.2-12.el7_2 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2016:0532 | 2016-03-31T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-423-1 | krb5 security update |
Debian DSA |
DSA-3466-1 | krb5 security update |
EUVD |
EUVD-2015-8506 | The xdr_nullstring function in lib/kadm5/kadm_rpc_xdr.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13.4 and 1.14.x before 1.14.1 does not verify whether '\0' characters exist as expected, which allows remote authenticated users to obtain sensitive information or cause a denial of service (out-of-bounds read) via a crafted string. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.7% (3.687% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.