# CVE-2024-3183: Freeipa: user can obtain a hash of the passwords of all domain users and perform offline brute force

> An attacker with a compromised principal can retrieve encrypted tickets to perform offline brute-force attacks and recover other users' passwords.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2024
- **Updated:** 20 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-3183, GHSA-8g25-xmmm-86qm, RHSA-2024:3756, RHSA-2024:3758, RHSA-2024:3760, RHSA-2024:3761, RHSA-2024:3775, UBUNTU-CVE-2024-3183

## What is CVE-2024-3183?

CVE-2024-3183 is a high-severity vulnerability in Redhat Enterprise Linux, published on 12 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2024-3183?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ipa` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client-common` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-common` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-python-compat` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-common` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-dns` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-trust-ad` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipaclient` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipalib` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipaserver` | Red Hat:enterprise_linux:7::client | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-dns` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-trust-ad` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipaserver` | Red Hat:enterprise_linux:7::computenode | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client-common` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-common` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-python-compat` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-common` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-dns` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-trust-ad` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipaclient` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipalib` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `python2-ipaserver` | Red Hat:enterprise_linux:7::server | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-client-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-python-compat` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |
| `ipa-server-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:4.6.8-5.el7_9.17 |

Products: Redhat Enterprise Linux, Redhat Enterprise Linux Aus, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Tus, Redhat Enterprise Linux Update Services for Sap Solutions.

## How do I fix CVE-2024-3183?

Apply the vendor's patch.

## Is CVE-2024-3183 being exploited?

There is no known exploitation of CVE-2024-3183 in the wild and no public exploit code.

Public exploit code:

- POC for CVE-2024-3183 (FreeIPA Rosting) (github_poc): https://github.com/Im10n/CVE-2024-3183-POC

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3183 and fix it if it is affected.

What it is: CVE-2024-3183 is a high-severity vulnerability in Redhat Enterprise Linux, published on 12 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3183 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3183/ (Markdown: https://insights.sbomify.com/CVE-2024-3183/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3183
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3183
- OSV: https://osv.dev/vulnerability/CVE-2024-3183

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3183/
Summaries are generated and may contain mistakes; the official description above is the record.