A vulnerability where applications using the MIT krb5 GSS-API library was discovered, that might allow applications using the MIT krb5 GSS-API library to accept authdata checksums with low-entropy derived keys.
An authenticated remote attacker that controls a legitimate service principal has a 1/256 chance of forging the AD-SIGNEDPATH signature if the TGT key is RC4, allowing it to use self-generated "evidence" tickets for S4U2Proxy, instead of tickets obtained from the user or with S4U2Self. Configurations using RC4 for the TGT key are believed to be rare.
An authenticated remote attacker has a 1/256 chance of forging AD-KDC-ISSUED signatures on authdata elements in tickets having an RC4 service key, resulting in privilege escalation against a service that relies on these signatures. There are no known uses of the KDC-ISSUED authdata container at this time.
This flaw affects MIT krb5 version 1.8 and newer. However, in environments exclusively using KDCs from 1.8 and newer, the KDC discards client-provided AD-KDC-ISSUED authdata and are not vulnerable to this issue.
A patch to correct this flaw, as well the other flaws noted in MITKRB5-SA-2010-007 are available from http://web.mit.edu/kerberos/advisories/2010-007-patch.txt.
This issue is known as CVE-2010-4020. The upstream announcement is available at http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2010-007.txt.
Red Hat would like to thank the MIT Kerberos Team for reporting this issue.
This issue has been addressed in following products:
Red Hat Enterprise Linux 6
Via RHSA-2010:0925 https://rhn.redhat.com/errata/RHSA-2010-0925.html
This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4 and 5.