krb5 was updated to fix five security issues.

These security issues were fixed:
- CVE-2014-5351: current keys returned when randomizing the keys for a service principal (bnc#897874)
- CVE-2014-5352: An authenticated attacker could cause a vulnerable
application (including kadmind) to crash or to execute arbitrary code (bnc#912002).
- CVE-2014-9421: An authenticated attacker could cause kadmind or other
vulnerable server application to crash or to execute arbitrary code (bnc#912002).
- CVE-2014-9422: An attacker who possess the key of a particularly named
principal (such as "kad/root") could impersonate any user to kadmind
and perform administrative actions as that user (bnc#912002).
- CVE-2014-9423: An attacker could attempt to glean sensitive
information from the four or eight bytes of uninitialized data output
by kadmind or other libgssrpc server application. Because MIT krb5
generally sanitizes memory containing krb5 keys before freeing it, it
is unlikely that kadmind would leak Kerberos key information, but it
is not impossible (bnc#912002).

This non-security issue was fixed:
- Work around replay cache creation race (bnc#898439).