dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2024-3183

HIGH · 8.1 CVSS v3.1 Published 2024-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In FreeIPA, when a Kerberos TGS-REQ is encrypted using the client's session key, the inner ticket is encrypted directly with the target principal's key. For user principals, this key derives from a per-principal salt and password hash. An attacker who compromises a principal can capture these tickets offline and perform brute force attacks to recover the target principal's password.

MitigationRotate passwords for affected principals immediately. Implement stronger password policies and consider implementing key derivation improvements in FreeIPA to prevent offline brute force attacks on captured TGS tickets.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 7.0= 8.0
Enterprise Linux AusOperating system
Affected:= 8.2= 8.4= 8.6
Enterprise Linux EusOperating system
Affected:= 8.8
Enterprise Linux TusOperating system
Affected:= 8.4= 8.6
Enterprise Linux Update Services For Sap SolutionsOperating system
Affected:= 8.4= 8.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if FreeIPA server is installed
    Run 'rpm -q ipa-server' or check for /usr/sbin/ipa-server-install
    Affected if Package is not installed - not affected; if installed, continue to version check
  2. Verify FreeIPA version against affected releases
    Run 'ipa --version' or 'rpm -q ipa-server' and compare to the affected version list (RHEL 7.0, 8.0, 8.2, 8.4, 8.6, 8.8)
    Affected if Installed version matches one of the affected RHEL versions listed in the CVE
  3. Confirm the system is an active IPA master
    Run 'ipa server-find' or check 'ipa env' to verify the host is configured as an IPA server
    Affected if System is not an IPA server - the vulnerability applies only to FreeIPA servers handling TGS requests
  4. Identify if user principals exist in the domain
    Run 'ipa user-find' to list user principals in the IPA domain
    Affected if No user principals exist - the attack vector targets user principals specifically, though service principals may also be affected
  5. Check Kerberos configuration for salts
    Inspect /etc/krb5.conf and /var/kerberos/krb5kdc/kdc.conf for 'salt' or 'salted' key derivation settings
    Affected if Configuration uses the default per-principal salt derivation (standard FreeIPA behavior) - the vulnerability is inherent to this method

A system is affected if it runs FreeIPA on a listed RHEL version, serves as an IPA master, and has user principals whose TGS tickets could be captured and subjected to offline brute force attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Rotate passwords for affected principals immediately. Implement stronger password policies and consider implementing key derivation improvements in FreeIPA to prevent offline brute force attacks on captured TGS tickets.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3183 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data