Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
mit-krb5: Multiple buffer overflows in krb5_aname_to_localname
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200406-21
(mit-krb5: Multiple buffer overflows in krb5_aname_to_localname)
The library function krb5_aname_to_localname() contains multiple buffer
overflows. This is only exploitable if explicit mapping or rules-based
mapping is enabled. These are not enabled as default.
With explicit mapping enabled, a possible hacker must authenticate using a
principal name listed in the explicit mapping list.
With rules-based mapping enabled, a possible hacker must first be able to create
arbitrary principal names either in the local realm Kerberos realm or in a
remote realm from which the local realm's service are reachable by
A possible hacker could use these vulnerabilities to execute arbitrary code with
the permissions of the user running mit-krb5, which could be the root user.
There is no known workaround at this time. All users are encouraged to
upgrade to the latest available version.
mit-krb5 users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=app-crypt/mit-krb5-1.3.3-r1"
# emerge ">=app-crypt/mit-krb5-1.3.3-r1"
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|# IBM eServer xSeries 345 Dual Xeon 2.8GHz 1.5GB 8670-L1X
|Lot 2x - IBM Lenovo ThinkSation S30 WorkStation (4352-H1U)+
|IBM SYSTEM X3650 M5 2.5 SERVER E5-2667V3 3.2GHZ 12 X 32GB 4 X 900GB 10K 6G
|# IBM eServer xSeries 346 2 Dual Xeon 2.8GHz 3GB 8840-01U
No Discussions have been posted on this vulnerability.