# CVE-2025-2487: 389-ds-base: null pointer dereference leads to denial of service > A privileged user can cause a denial of service in the 389-ds-base LDAP server by triggering a null pointer dereference during a Modify DN operation. - **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Mar 2025 - **Updated:** 30 Jun 2026 - **Also known as:** ALSA-2025:4491, ALSA-2025:7395, DEBIAN-CVE-2025-2487, GHSA-33fh-4pvq-9x35, GHSA-426r-w669-66gw, OESA-2025-1373, OESA-2025-1374, RHSA-2025:3663, RHSA-2025:3670, RHSA-2025:4491, RHSA-2025:7395, RLSA-2025:4491, RLSA-2025:7395, UBUNTU-CVE-2025-2487, openSUSE-SU-2025:14934-1 ## What is CVE-2025-2487? CVE-2025-2487 is a medium-severity vulnerability in Red Hat Directory Server 12, published on 18 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description A flaw was found in the 389-ds-base LDAP Server. This issue occurs when issuing a Modify DN LDAP operation through the ldap protocol, when the function return value is not tested and a NULL pointer is dereferenced. If a privileged user performs a ldap MODDN operation after a failed operation, it could lead to a Denial of Service (DoS) or system crash. Weakness: CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2025-2487? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | AlmaLinux:9 | All versions | 2.5.2-9.el9_5 | | `389-ds-base` | AlmaLinux:9 | All versions | 2.6.1-8.el9_6 | | `389-ds-base-devel` | AlmaLinux:9 | All versions | 2.5.2-9.el9_5 | | `389-ds-base-devel` | AlmaLinux:9 | All versions | 2.6.1-8.el9_6 | | `389-ds-base-libs` | AlmaLinux:9 | All versions | 2.5.2-9.el9_5 | | `389-ds-base-libs` | AlmaLinux:9 | All versions | 2.6.1-8.el9_6 | | `389-ds-base-snmp` | AlmaLinux:9 | All versions | 2.5.2-9.el9_5 | | `389-ds-base-snmp` | AlmaLinux:9 | All versions | 2.6.1-8.el9_6 | | `python3-lib389` | AlmaLinux:9 | All versions | 2.5.2-9.el9_5 | | `python3-lib389` | AlmaLinux:9 | All versions | 2.6.1-8.el9_6 | | `389-ds-base` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-debuginfo` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-debugsource` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-devel` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-libs` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-snmp` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `cockpit-389-ds` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `python3-lib389` | Red Hat:directory_server_eus:12.4::el9 | All versions | 0:2.4.5-12.module+el9dsrv+22976+238a2ead | | `389-ds-base` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-snmp-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-snmp-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `python3-lib389` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.5.2-9.el9_5 | | `python3-lib389` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.6.1-8.el9_6 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.5.2-9.el9_5 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.6.1-8.el9_6 | ## How do I fix CVE-2025-2487? Apply the vendor's patch. ## Is CVE-2025-2487 being exploited? There is no known exploitation of CVE-2025-2487 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-2487 and fix it if it is affected. What it is: CVE-2025-2487 is a medium-severity vulnerability in Red Hat Directory Server 12, published on 18 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-2487 in the wild and no public exploit code. Affected product: Red Hat Directory Server 12. 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-2025-2487/ (Markdown: https://insights.sbomify.com/CVE-2025-2487/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2487 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2487 - OSV: https://osv.dev/vulnerability/CVE-2025-2487 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-2487/ Summaries are generated and may contain mistakes; the official description above is the record.