MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a ‘\0’ character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-bounds read) by omitting the ‘\0’ character, related to appl/user_user/server.c and lib/krb5/krb/recvauth.c.
krbdev.mit.edu/rt/Ticket/Display.html?id=8050
lists.opensuse.org/opensuse-updates/2015-03/msg00061.html
rhn.redhat.com/errata/RHSA-2015-0794.html
www.mandriva.com/security/advisories?name=MDVSA-2015:069
www.oracle.com/technetwork/topics/security/bulletinjan2015-2370101.html
www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
www.securityfocus.com/bid/74042
www.ubuntu.com/usn/USN-2810-1
github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec
lists.debian.org/debian-lts-announce/2018/01/msg00040.html