A vulnerability was found in FreeIPA in how the initial implementation of MS-SFU by MIT Kerberos was missing a condition for granting the forwardable flag on S4U2Self tickets. Fixing this mistake required adding a special case for the check_allowed_to_delegate() function: If the target service argument is NULL, then it means the KDC is probing for general constrained delegation rules and not checking a specific S4U2Proxy request.
In FreeIPA 4.11.0, the behavior of ipadb_match_acl() was modified to match the changes from upstream MIT Kerberos 1.20. However, a mistake resulting in this mechanism applies in cases where the target service argument is set AND where it is unset. This results in S4U2Proxy requests being accepted regardless of whether or not there is a matching service delegation rule.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | RedHat | idm:DL1-8100020240528133707.823393f5 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | idm:DL1-8080020240530051744.b0a6ceea | * |
| Red Hat Enterprise Linux 9 | RedHat | ipa-0:4.11.0-15.el9_4 | * |
| Red Hat Enterprise Linux 9.2 Extended Update Support | RedHat | ipa-0:4.10.1-12.el9_2.2 | * |
| Freeipa | Ubuntu | mantic | * |
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: