Software Engineering Institute

The MIT krb5 Security Advisory 2011-006 states:

CVE-2011-1527: In releases krb5-1.9 and later, the KDC can crash due to a null pointer dereference if configured to use the LDAP back end. A trigger condition is publicly known but not known to be widely circulated.

CVE-2011-1528: In releases krb5-1.8 and later, the KDC can crash due to an assertion failure. No exploit is known to exist, but there is public evidence that the unidentified trigger condition occurs in the field.

CVE-2011-1529: In releases krb5-1.8 and later, the KDC can crash due to a null pointer dereference. No exploit is known to exist.

CVE-2011-4151: In releases krb5-1.8 through krb5-1.8.4, the KDC can crash due to an assertion failure if configured to use the Berkeley DB ("db2") back end.

The MIT krb5 Security Advisory 2011-006 states:

CVE-2011-1527: An unauthenticated remote attacker can crash a KDC daemon via null pointer dereference if the KDC is configured to use the LDAP back end. (This is not the default configuration.)

CVE-2011-1528: An unauthenticated remote attacker can crash a KDC daemon via assertion failure.

CVE-2011-1529: An unauthenticated remote attacker can crash a KDC daemon via null pointer dereference.

CVE-2011-4151: An unauthenticated remote attacker can crash a KDC daemon via assertion failure if the KDC is configured to use the Berkeley DB ("db2") back end.

The MIT krb5 Security Advisory 2011-006 states:

• The patch for krb5-1.9.x is available at: http://web.mit.edu/kerberos/advisories/2011-006-patch.txt
  A PGP-signed patch is available at: http://web.mit.edu/kerberos/advisories/2011-006-patch.txt.asc
  
• The patch for krb5-1.8.x is available at: http://web.mit.edu/kerberos/advisories/2011-006-patch-r18.txt
  A PGP-signed patch is available at: http://web.mit.edu/kerberos/advisories/2011-006-patch-r18.txt.asc