The krb5_db2_lockout_audit function in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) 1.8 through 1.8.4, when the db2 (aka Berkeley DB) back end is used, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via unspecified vectors, a different vulnerability than CVE-2011-1528.

The remote Solaris system is missing necessary patches to address security updates :

  - The krb5_ldap_lockout_audit function in the Key     Distribution Center (KDC) in MIT Kerberos 5 (aka krb5)     1.8 through 1.8.4 and 1.9 through 1.9.1, when the LDAP     back end is used, allows remote attackers to cause a     denial of service (assertion failure and daemon exit)     via unspecified vectors, related to the locked_check_p     function. NOTE: the Berkeley DB vector is covered by     CVE-2011-4151. (CVE-2011-1528)

  - The lookup_lockout_policy function in the Key     Distribution Center (KDC) in MIT Kerberos 5 (aka krb5)     1.8 through 1.8.4 and 1.9 through 1.9.1, when the db2     (aka Berkeley DB) or LDAP back end is used, allows     remote attackers to cause a denial of service (NULL     pointer dereference and daemon crash) via vectors that     trigger certain process_as_req errors. (CVE-2011-1529)

  - The krb5_db2_lockout_audit function in the Key     Distribution Center (KDC) in MIT Kerberos 5 (aka krb5)     1.8 through 1.8.4, when the db2 (aka Berkeley DB) back     end is used, allows remote attackers to cause a denial     of service (assertion failure and daemon exit) via     unspecified vectors, a different vulnerability than     CVE-2011-1528. (CVE-2011-4151)

The remote host is affected by the vulnerability described in GLSA-201201-13 (MIT Kerberos 5: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in MIT Kerberos 5. Please       review the CVE identifiers referenced below for details.
  Impact :

    A remote attacker may be able to execute arbitrary code with the       privileges of the administration daemon or the Key Distribution Center       (KDC) daemon, cause a Denial of Service condition, or possibly obtain       sensitive information. Furthermore, a remote attacker may be able to       spoof Kerberos authorization, modify KDC responses, forge user data       messages, forge tokens, forge signatures, impersonate a client, modify       user-visible prompt text, or have other unspecified impact.
  Workaround :

    There is no known workaround at this time.

ID	Name	Product	Family	Severity
80650	Oracle Solaris Third-Party Patch Update : kerberos (multiple_input_validation_vulnerabilities_in)	Nessus	Solaris Local Security Checks	high
57655	GLSA-201201-13 : MIT Kerberos 5: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium

Detections

Analytics

CVE-2011-4151

high

Tenable Plugins

high

medium