The kerberos project reports: In build_principal_va(), use k5memdup0() instead of strdup() to make a copy of the realm, to ensure that we allocate the correct number of bytes and do not read past the end of the input string. This bug affects krb5_build_principal(), krb5_build_principal_va(), and krb5_build_principal_alloc_va(). krb5_build_principal_ext() is not affected. CVE-2015-2697: In MIT krb5 1.7 and later, an authenticated attacker may be able to cause a KDC to crash using a TGS request with a large realm field beginning with a null byte. If the KDC attempts to find a referral to answer the request, it constructs a principal name for lookup using krb5_build_principal() with the requested realm. Due to a bug in this function, the null byte causes only one byte be allocated for the realm field of the constructed principal, far less than its length. Subsequent operations on the lookup principal may cause a read beyond the end of the mapped memory region, causing the KDC process to crash. External reference: https://github.com/krb5/krb5/commit/f0c094a1b745d91ef2f9a4eae2149aac026a5789
Created krb5 tracking bugs for this issue: Affects: fedora-all [bug 1275872]
https://bodhi.fedoraproject.org/updates/FEDORA-2015-be1b87a3b7 https://bodhi.fedoraproject.org/updates/FEDORA-2015-e6791ce284 https://bodhi.fedoraproject.org/updates/FEDORA-2015-ae56161457 Unfortunately I don't see an easy way to associate these bugs with those.