CVE-2024-3183: Freeipa: user can obtain a hash of the passwords of all domain users and perform offline brute force
A low-privileged user can obtain a hash of the passwords of all domain users and perform offline brute force (kerberoasting).
It was found that all users who have TGT Kerberos tickets can request TGS for another user's principal. And since the “krbPrincipalKey” value for users is created based on their password, kerberoasting attacks on TGS tickets are possible. A potential attacker can brute force the password by requesting TGS for other users.
Other sources
A vulnerability was found in FreeIPA in a way when a Kerberos TGS-REQ is encrypted using the client’s session key. This key is different for each new session, which protects it from brute force attacks. However, the ticket it contains is encrypted using the target principal key directly. For user principals, this key is a hash of a public per-principal randomly-generated salt and the user’s password. If a principal is compromised it means the attacker would be able to retrieve tickets encrypted to any principal, all of them being encrypted by their own key directly. By taking these tickets and salts offline, the attacker could run brute force attacks to find character strings able to decrypt tickets when combined to a principal salt (i.e. find the principal’s password).
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-3183?
CVE-2024-3183 is considered a low severity vulnerability.
How do I fix CVE-2024-3183?
To fix CVE-2024-3183, you should upgrade to FreeIPA version 4.11.2 or 4.12.1 or ensure your Red Hat Enterprise Linux is updated to the latest supported version.
Who is affected by CVE-2024-3183?
CVE-2024-3183 affects all users within a domain who have TGT Kerberos tickets.
What impact does CVE-2024-3183 have on users?
CVE-2024-3183 allows low-privileged users to obtain password hashes of all domain users, potentially enabling offline brute force attacks.
Is there a workaround for CVE-2024-3183?
There is no official workaround for CVE-2024-3183, so it is recommended to apply the necessary updates.