Vulnerability in freeipa
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2024-3183 has been found in freeipa.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "freeipa UBUNTU-CVE-2024-3183" on the vendor's site.
UBUNTU-CVE-2024-3183 (freeipa)
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in freeipa.
Check the vendor advisory for the affected versions of freeipa.
Severity: ?. Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'freeipa' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'freeipa' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
freeipaを grep し、稼働しているサービス・バージョンを把握する。 -
2
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Ubuntu:Pro:14.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:Pro:16.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:18.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:20.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:22.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:24.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:25.10freeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:26.04:LTSfreeipa |
All versions→ Not listed |
Not listed |
| Ubuntu:26.10freeipa |
All versions→ Not listed |
Not listed |
This record does not list fixed versions. Check the article or the vendor advisory in the references for whether and where it is fixed.
Original description The description as published by the source.
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).
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- report ubuntu.com
- report cve.org
- report bugzilla.redhat.com