Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2024-3183 is a high-severity Use of Password Hash With Insufficient Computational Effort (CWE-916) vulnerability in Redhat Enterprise Linux Aus. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and IA-5 (Authenticator Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A vulnerability exists in FreeIPA's handling of Kerberos TGS-REQ messages, where the contained ticket is encrypted directly with the target principal's key rather than the client's session key. For user principals this key is derived from a public per-principal salt combined with the user's password, exposing the system to offline brute-force attacks once any principal is compromised. The flaw is tracked as CVE-2024-3183 and carries a CVSS 3.1 score of 8.1.
An attacker with a compromised principal can request and capture service tickets encrypted to arbitrary other principals. These tickets, together with the publicly available salts, can be processed offline to recover the corresponding passwords, granting the attacker access to additional accounts without further interaction with the FreeIPA server.
Red Hat has published errata RHSA-2024:3754 through RHSA-2024:3758 that address the issue in affected products. The EPSS score has remained at 0.2123 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-31775
Vulnerability Data
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…
more
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).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.4.2
Mitigating Controls (NIST 800-53 r5) AI
Cryptographic protection mandates selection and use of approved algorithms whose parameters can include sufficient work factors for password hashing.
Authenticator management requires secure generation, distribution, and storage of passwords, directly enforcing computationally expensive hashing schemes.
Protection of information at rest requires cryptographic safeguards on stored password hashes, reducing exposure to offline cracking.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Proper password hashing is a direct instance of using cryptographic hashes to protect data-at-rest.
Secure development practices explicitly include selection and configuration of strong, computationally expensive password hashes.
Authentication policies may reference password handling but do not address storage or computational cost of hashes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requires secure handling of authentication information, which includes choosing strong password hashing schemes.
Requires appropriate use of cryptography, which encompasses selecting strong hashing algorithms for passwords.
Secure coding practices include implementing password storage with adequate computational effort.
Mandates secure authentication mechanisms, directly addressing the need for computationally strong password hashes.