CVE-2014-5351: Low severity kerberos vulnerability
It was reported that if a privileged user randomized the keys for a service principal, the old key would be returned to them. This could lead to ticket forgery attacks on the service in question.
This issue has been fixed in upstream version 1.13. Red Hat Enterprise Linux 6 and 7 are affected.
Full details from the upstream report:
"" An authenticated remote attacker can retrieve the current keys for a service principal when generating a new set of keys for that principal. The attacker needs to be authenticated as a user who has the elevated privilege for randomizing the keys of other principals.
Normally, when a Kerberos administrator randomizes the keys of a service principal, kadmind returns only the new keys. This prevents an administrator who lacks legitimate privileged access to a service from forging tickets to authenticate to that service. If the "keepold" flag to the kadmin randkey RPC operation is true, kadmind retains the old keys in the KDC database as intended, but also unexpectedly returns the old keys to the client, which exposes the service to ticket forgery attacks from the administrator.
A mitigating factor is that legitimate clients of the affected service will start failing to authenticate to the service once they begin to receive service tickets encrypted in the new keys. The affected service will be unable to decrypt the newly issued tickets, possibly alerting the legitimate administrator of the affected service. ""
Upstream patch:
https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca
References:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=8018
Other sources
The kadm5randkeyprincipal3 function in lib/kadm5/srv/svrprincipal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-5351?
CVE-2014-5351 is considered a high-severity vulnerability due to its potential for ticket forgery attacks.
How do I fix CVE-2014-5351?
To fix CVE-2014-5351, upgrade to MIT Kerberos 5 version 1.13 or later.
Which software is affected by CVE-2014-5351?
CVE-2014-5351 affects MIT Kerberos 5 version 1.12.2 and older, particularly on Red Hat Enterprise Linux 6 and 7.
What attack vector is associated with CVE-2014-5351?
CVE-2014-5351 can be exploited through ticket forgery attacks if a privileged user incorrectly randomizes keys.
Has CVE-2014-5351 been fixed?
Yes, CVE-2014-5351 has been fixed in upstream version 1.13 of the software.