The check_rpcsec_auth function in kadmin/server/kadm_rpc_svc.c in kadmind in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 allows remote authenticated users to bypass a kadmin/* authorization check and obtain administrative access by leveraging access to a two-component principal with an initial kadmind substring, as demonstrated by a ka/x principal.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Kerberos_5 | Mit | 1.11 (including) | 1.11 (including) |
Kerberos_5 | Mit | 1.11.1 (including) | 1.11.1 (including) |
Kerberos_5 | Mit | 1.11.2 (including) | 1.11.2 (including) |
Kerberos_5 | Mit | 1.11.3 (including) | 1.11.3 (including) |
Kerberos_5 | Mit | 1.11.4 (including) | 1.11.4 (including) |
Kerberos_5 | Mit | 1.11.5 (including) | 1.11.5 (including) |
Kerberos_5 | Mit | 1.12 (including) | 1.12 (including) |
Kerberos_5 | Mit | 1.12.1 (including) | 1.12.1 (including) |
Kerberos_5 | Mit | 1.12.2 (including) | 1.12.2 (including) |
Kerberos_5 | Mit | 1.13 (including) | 1.13 (including) |
Red Hat Enterprise Linux 6 | RedHat | krb5-0:1.10.3-37.el6_6 | * |
Red Hat Enterprise Linux 7 | RedHat | krb5-0:1.12.2-14.el7 | * |
Krb5 | Ubuntu | devel | * |
Krb5 | Ubuntu | lucid | * |
Krb5 | Ubuntu | precise | * |
Krb5 | Ubuntu | trusty | * |
Krb5 | Ubuntu | upstream | * |
Krb5 | Ubuntu | utopic | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: