# CVE-2024-11029: Freeipa: administrative user data leaked through systemd journal > FreeIPA leaks administrative credentials to the systemd journal during installation, allowing attackers with journal access to steal admin passwords. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Jan 2025 - **Updated:** 20 Nov 2025 - **Also known as:** ALSA-2025:0334, DEBIAN-CVE-2024-11029, GHSA-45q7-xhfm-xqjp, RHSA-2025:0334, UBUNTU-CVE-2024-11029 ## What is CVE-2024-11029? CVE-2024-11029 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was found in the FreeIPA API audit, where it sends the whole FreeIPA command line to journalctl. As a consequence, during the FreeIPA installation process, it inadvertently leaks the administrative user credentials, including the administrator password, to the journal database. In the worst-case scenario, where the journal log is centralized, users with access to it can have improper access to the FreeIPA administrator credentials. Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) ## Which versions are affected by CVE-2024-11029? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ipa-client` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-client-common` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-client-epn` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-client-samba` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-common` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-selinux` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-selinux-luna` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-selinux-nfast` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-server` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-server-common` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-server-dns` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa-server-trust-ad` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `python3-ipaclient` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `python3-ipalib` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `python3-ipaserver` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `python3-ipatests` | AlmaLinux:9 | All versions | 4.12.2-1.el9_5.3 | | `ipa` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-client` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-client-common` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-client-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-client-epn` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-client-samba` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-common` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-selinux` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-selinux-luna` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-selinux-nfast` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server-common` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server-dns` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server-trust-ad` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `ipa-server-trust-ad-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `python3-ipaclient` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `python3-ipalib` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `python3-ipaserver` | Red Hat:enterprise_linux:9::appstream | All versions | 0:4.12.2-1.el9_5.3 | | `python3-ipatests` | Red Hat:enterprise_linux:9::crb | All versions | 0:4.12.2-1.el9_5.3 | ## How do I fix CVE-2024-11029? Apply the vendor's patch. ## Is CVE-2024-11029 being exploited? There is no known exploitation of CVE-2024-11029 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-11029 and fix it if it is affected. What it is: CVE-2024-11029 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-11029 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. 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-11029/ (Markdown: https://insights.sbomify.com/CVE-2024-11029/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11029 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11029 - OSV: https://osv.dev/vulnerability/CVE-2024-11029 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-11029/ Summaries are generated and may contain mistakes; the official description above is the record.