CVE-2024-2698
HighCVSS 8.8Exploitation Probability (EPSS)
Elevated risk52th percentile - higher than 52% of all known CVEs
Summary
A vulnerability was found in FreeIPA related to the initial MS-SFU implementation in MIT Kerberos, which lacked a condition for granting the "forwardable" flag on S4U2Self tickets. In FreeIPA 4.11.0, a modification to ipadb_match_acl() caused the mechanism to apply both when the target service argument is set and unset, resulting in S4U2Proxy requests being accepted regardless of a matching delegation rule.
Risk Assessment
An attacker could exploit improper delegation to gain unauthorized access to services in the domain, potentially leading to privilege escalation within the FreeIPA environment.
Recommendation
Update FreeIPA to a patched version. Review service delegation rules and restrict the ability to create S4U2Proxy requests.
Other vulnerabilities in FreeIPA
See all- CVE-2017-11191High
FreeIPA 4.x with API version 2.213 allows remote authenticated users to bypass intended account-locking restrictions via an unlock action with an old session ID (for the same user account) that had been created for an earlier session.
- CVE-2015-5179High
FreeIPA might display user data improperly via vectors involving non-printable characters.
- CVE-2016-7030High
FreeIPA uses a default password policy that locks an account after 5 unsuccessful authentication attempts. This allows remote attackers to cause a denial of service by locking out the account in which system services run on.
- CVE-2016-5414High
FreeIPA version 4.4.0 allows remote attackers to request an arbitrary SAN name for services.
- CVE-2026-76578Critical
A flaw was found in FreeIPA. The self-managed OTP token ACI does not require authentication and does not restrict which attributes may be added alongside the token entry. An unauthenticated LDAP client can exploit this, combined with a related flaw in the underlying directory server's ACI evaluation (tracked separately), to create an arbitrary attacker-controlled Kerberos principal and have it added to the administrators group. This allows a remote, unauthenticated attacker to obtain genuine FreeIPA administrator-group membership and perform administrative operations against the directory and, on SID-enabled deployments, other IdM services.
- CVE-2026-11861Critical
A flaw was found in FreeIPA. When a trust relationship is configured with Active Directory, AD users can bypass authentication for FreeIPA services by impersonating a client name in the TGS due to missing PAC certificate verification. This could allow an authenticated AD user to escalate privileges within the FreeIPA domain.
- CVE-2025-4404Critical
A privilege escalation from host to domain vulnerability was found in FreeIPA. The lack of uniqueness validation for the `krbCanonicalName` attribute of the admin account allows creating a service with the same canonical name as the REALM admin. A successful attack lets the attacker obtain a Kerberos ticket with admin@REALM credentials.
- CVE-2015-5284Critical
In FreeIPA before version 4.2.2, the ipa-kra-install script places the CA agent certificate and private key in /etc/httpd/alias/kra-agent.pem, which is world readable.
- CVE-2026-115221Medium
A flaw was found in FreeIPA. An improper authorization check allows an authenticated host to retrieve and revoke digital certificates assigned to other users or services. This issue occurs because FreeIPA verifies ownership solely by matching the host name to the certificate's subject Common Name (CN), without confirming actual ownership in the directory service. Consequently, an enrolled host can disrupt services by revoking certificates belonging to other entities.
- CVE-2026-18147High
A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the FreeIPA/IdM Web UI password reset page. An unauthenticated remote attacker can exploit it by enticing a victim to click a crafted link and complete a password reset, allowing injection and execution of arbitrary JavaScript in the victim's session.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

