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 vulnerabilities
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200409-09
(MIT krb5: Multiple vulnerabilities)
The implementation of the Key Distribution Center (KDC) and the MIT krb5
library contain double-free vulnerabilities, making client programs as well
as application servers vulnerable.
The ASN.1 decoder library is vulnerable to a denial of service attack,
including the KDC.
The double-free vulnerabilities could permit a possible hacker to execute
arbitrary code on a KDC host and hosts running krb524d or vulnerable
services. In the case of a KDC host, this can lead to a compromise of the
entire Kerberos realm. Furthermore, a possible hacker impersonating a legitimate
KDC or application server can potentially execute arbitrary code on
A possible hacker can cause a denial of service for a KDC or application server
and clients, the latter if impersonating a legitimate KDC or application
There is no known workaround at this time.
All mit-krb5 users should upgrade to the latest stable version:
# emerge sync
# emerge -pv ">=app-crypt/mit-krb5-1.3.4"
# emerge ">=app-crypt/mit-krb5-1.3.4"
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|Dell PowerEdge T610 2X5550-2.66GHz Windows Server 2008
|Dell R720 Dual E5-2695 v2 12C 2.4GHz 384GB 8x 600GB 15K SAS iDRAC 2.5in Rails
|Dell R720 Dual E5-2695 v2 12C 2.4GHz 128GB 8x 300GB 15K SAS iDRAC 2.5in Rails
|Dell R720 Dual E5-2695 v2 12C 2.4GHz 32GB 8x 1.2TB SAS iDRAC 2.5in Rails
No Discussions have been posted on this vulnerability.