A privilege escalation from host to domain vulnerability was found in the FreeIPA project. The FreeIPA package fails to validate the uniqueness of the krbCanonicalName for the admin account by default, allowing users to create services with the same canonical name as the REALM admin. When a successful attack happens, the user can retrieve a Kerberos ticket in the name of this service, containing the admin@REALM credential. This flaw allows an attacker to perform administrative tasks over the REALM, leading to access to sensitive data and sensitive data exfiltration.
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | ipa-0:4.12.2-15.el10_0.1 | * |
| Red Hat Enterprise Linux 7 Extended Lifecycle Support | RedHat | ipa-0:4.6.8-5.el7_9.18 | * |
| Red Hat Enterprise Linux 8 | RedHat | idm:client-8100020250603150652.143e9e98 | * |
| Red Hat Enterprise Linux 8 | RedHat | idm:DL1-8100020250603134209.823393f5 | * |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | RedHat | idm:client-8020020250609031831.50ea30f9 | * |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | RedHat | idm:DL1-8020020250609030144.792f4060 | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | idm:client-8040020250609101903.f153676a | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | idm:DL1-8040020250609095221.5b01ab7e | * |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | RedHat | idm:client-8060020250606060927.c1533a64 | * |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | RedHat | idm:DL1-8060020250606060504.ada582f1 | * |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | RedHat | idm:client-8060020250606060927.c1533a64 | * |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | RedHat | idm:DL1-8060020250606060504.ada582f1 | * |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | RedHat | idm:client-8060020250606060927.c1533a64 | * |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | RedHat | idm:DL1-8060020250606060504.ada582f1 | * |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | RedHat | idm:client-8080020250604195510.e581a9e4 | * |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | RedHat | idm:DL1-8080020250604202433.b0a6ceea | * |
| Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | RedHat | idm:client-8080020250604195510.e581a9e4 | * |
| Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | RedHat | idm:DL1-8080020250604202433.b0a6ceea | * |
| Red Hat Enterprise Linux 9 | RedHat | ipa-0:4.12.2-14.el9_6.1 | * |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | RedHat | ipa-0:4.9.8-11.el9_0.4 | * |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | RedHat | ipa-0:4.10.1-12.el9_2.4 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | ipa-0:4.11.0-15.el9_4.5 | * |
Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection. A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.