CVE-2024-3183VulnerabilityPublished 12 Jun 2024Updated 20 Nov 2025

CVE-2024-3183: Weak Password Hashing

Source CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-3183, organizations should prioritize applying any available patches or updates from FreeIPA or Red Hat as soon as they are released. In the absence of immediate patches, administrators should enforce strong password policies to increase the complexity and length of user passwords, making brute force attacks more difficult. Implementing multi-factor authentication (MFA) can reduce the risk of credential compromise. Monitoring and alerting on unusual authentication patterns or repeated failed attempts can help detect brute force activities early. Additionally, consider limiting the exposure of Kerberos tickets and salts by restricting access to sensitive authentication data and employing network segmentation. Using stronger key derivation functions with higher computational effort for password hashing within FreeIPA would be a long-term fix. Regularly auditing and rotating credentials, combined with user education on password hygiene, will further reduce risk. Finally, organizations should review their incident response plans to quickly address any potential compromise stemming from this vulnerability.

Description

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).

Impact

The primary impact of CVE-2024-3183 is the potential compromise of user credentials within FreeIPA-managed environments. Successful exploitation allows attackers to perform offline brute force attacks against password hashes derived from encrypted Kerberos tickets, potentially recovering user passwords. This can lead to unauthorized access, privilege escalation, and lateral movement within an organization's network. Confidentiality is severely impacted as attackers can decrypt sensitive tickets and impersonate users. Integrity is also at risk because attackers can forge authentication tokens. Although availability is not directly affected, the breach of authentication mechanisms can lead to broader security incidents, including data breaches and disruption of services. Organizations relying on FreeIPA for identity and access management, especially those in sectors with sensitive data or critical infrastructure, face significant risks. The vulnerability could undermine trust in authentication systems and lead to regulatory and compliance consequences if exploited.

References

Community reviews

Loading reviews…