This update upgrades freeipa to version 4.12.4-alt1. Security Fix(es): * BDU:2025-04863: Уязвимость централизованной системы по управлению …
This update upgrades freeipa to version 4.12.4-alt1. Security Fix(es): * BDU:2025-04863: Уязвимость централизованной системы по управлению идентификацией пользователей FreeIPA, связанная с неправильным контролем доступа, позволяющая нарушителю повысить свои привилегии до уровня администратора домена и оказать воздействие на конфиденциальность целостность и доступость защищаемой информации * CVE-2025-4404: 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.
https://cwe.mitre.org/data/definitions/1220.html →Open in CWE collection →In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
https://capec.mitre.org/data/definitions/1.html →Open in CAPEC collection →An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
https://capec.mitre.org/data/definitions/180.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| freeipa | Tracked | |
| freeipa | Tracked | |
| freeipa | Tracked | |
| freeipa | Tracked | |
| freeipa-client | Tracked | |
| freeipa-client-automount | Tracked | |
| freeipa-client-common | Tracked | |
| freeipa-client-epn | Tracked | |
| freeipa-client-samba | Tracked | |
| freeipa-common | Tracked | |
| freeipa-server | Tracked | |
| freeipa-server-common | Tracked | |
| freeipa-server-dns | Tracked | |
| freeipa-server-trust-ad | Tracked | |
| python3-module-freeipa | Tracked | |
| python3-module-ipaclient | Tracked | |
| python3-module-ipaserver | Tracked | |
| python3-module-ipatests | Tracked |