Skip to content
Fencer Intel
medium 4.9

CVE-2025-2487 json

389-ds-base: null pointer dereference leads to denial of service

published last yr. modified 4d ago also EUVD-2025-6692

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat Directory Server 12.4 EUS for RHEL 9 9040020250325181857.1674d574
  • Red Hat Red Hat Enterprise Linux 9 0:2.5.2-9.el9_5, 0:2.6.1-8.el9_6
  • Red Hat Red Hat Enterprise Linux 9.4 Extended Update Support 0:2.4.5-14.el9_4
  • 389-ds-base Debian 13 3.1.2+dfsg1-1

debian advisories DEBIAN-CVE-2025-2487

  • 389-ds-base RHEL 9 2.6.1-8.el9_6
  • python3-lib389 RHEL 9 2.6.1-8.el9_6
  • 389-ds-base-libs RHEL 9 2.6.1-8.el9_6
  • 389-ds-base-snmp RHEL 9 2.6.1-8.el9_6
  • 389-ds-base RHEL 9 2.5.2-9.el9_5
  • python3-lib389 RHEL 9 2.5.2-9.el9_5
  • 389-ds-base-libs RHEL 9 2.5.2-9.el9_5
  • 389-ds-base-snmp RHEL 9 2.5.2-9.el9_5

red hat advisories RHSA-2025:7395RHSA-2025:4491RHSA-2025:3670RHSA-2025:3663

  • 389-ds openSUSE Tumbleweed 3.1.2~git55.7fbd4526-1.1

opensuse advisories openSUSE-SU-2025:14934-1

  • 389-ds-base AlmaLinux 9 2.6.1-8.el9_6
  • python3-lib389 AlmaLinux 9 2.6.1-8.el9_6
  • 389-ds-base-libs AlmaLinux 9 2.6.1-8.el9_6
  • 389-ds-base-snmp AlmaLinux 9 2.6.1-8.el9_6
  • 389-ds-base AlmaLinux 9 2.5.2-9.el9_5
  • python3-lib389 AlmaLinux 9 2.5.2-9.el9_5
  • 389-ds-base-libs AlmaLinux 9 2.5.2-9.el9_5
  • 389-ds-base-snmp AlmaLinux 9 2.5.2-9.el9_5

almalinux advisories ALSA-2025:7395ALSA-2025:4491

  • 389-ds-base Rocky Linux 9 2.6.1-8.el9_6
  • 389-ds-base Rocky Linux 9 2.5.2-9.el9_5

rocky linux advisories RLSA-2025:7395RLSA-2025:4491

Is CVE-2025-2487 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-2487 updated cvss 4.9

389-ds-base: null pointer dereference leads to denial of service

  • Red Hat Enterprise Linux 6 389-ds-base, 389-ds-base-libs Red Hat Enterprise Linux 7 389-ds-base, 389-ds-base-libs, 389-ds-base-snmp Red Hat Enterprise Linux 8 389-ds-base, cockpit-389-ds, python3-lib389, 389-ds-base-libs, 389-ds-base-snmp, 389-ds-base-legacy-tools
    affected: workaround, no fix planned “Currently, no mitigation is available for this vulnerability.”
  • Red Hat CodeReady Linux Builder (v. 9) 389-ds-base-devel 2.5.2-9.el9_5, 389-ds-base-debuginfo 2.5.2-9.el9_5, 389-ds-base-debugsource 2.5.2-9.el9_5, 389-ds-base-libs-debuginfo 2.5.2-9.el9_5, 389-ds-base-snmp-debuginfo 2.5.2-9.el9_5
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:4491
  • Red Hat CodeReady Linux Builder EUS (v.9.4) 389-ds-base-devel 2.4.5-14.el9_4, 389-ds-base-debuginfo 2.4.5-14.el9_4, 389-ds-base-debugsource 2.4.5-14.el9_4, 389-ds-base-libs-debuginfo 2.4.5-14.el9_4, 389-ds-base-snmp-debuginfo 2.4.5-14.el9_4
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:3663
  • Red Hat Directory Server 12.4 EUS for RHEL 9 389-ds-base 2.4.5-12.module+el9dsrv+22976+238a2ead, cockpit-389-ds 2.4.5-12.module+el9dsrv+22976+238a2ead, python3-lib389 2.4.5-12.module+el9dsrv+22976+238a2ead, 389-ds-base-libs 2.4.5-12.module+el9dsrv+22976+238a2ead, 389-ds-base-snmp 2.4.5-12.module+el9dsrv+22976+238a2ead
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:3670
  • Red Hat Enterprise Linux AppStream (v. 9) 389-ds-base 2.5.2-9.el9_5, 389-ds-base 2.6.1-8.el9_6, python3-lib389 2.5.2-9.el9_5, python3-lib389 2.6.1-8.el9_6, 389-ds-base-libs 2.5.2-9.el9_5, 389-ds-base-libs 2.6.1-8.el9_6, +2 more
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:4491
  • Red Hat Enterprise Linux AppStream EUS (v.9.4) 389-ds-base 2.4.5-14.el9_4, python3-lib389 2.4.5-14.el9_4, 389-ds-base-libs 2.4.5-14.el9_4
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:3663
  • Red Hat Enterprise Linux CodeReady Linux Builder (v. 9) 389-ds-base-devel 2.6.1-8.el9_6, 389-ds-base-debuginfo 2.6.1-8.el9_6, 389-ds-base-debugsource 2.6.1-8.el9_6, 389-ds-base-libs-debuginfo 2.6.1-8.el9_6, 389-ds-base-snmp-debuginfo 2.6.1-8.el9_6
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:7395
  • Red Hat Directory Server 12 389-ds-base Red Hat Enterprise Linux 10 389-ds-base
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected products

  • 389ds 389-ds-base
  • Red Hat Red Hat Directory Server 12.4 EUS for RHEL 9
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Red Hat Enterprise Linux 9.4 Extended Update Support
  • Red Hat Red Hat Directory Server 12
  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Enterprise Linux 6
  • Red Hat Red Hat Enterprise Linux 7
  • Red Hat Red Hat Enterprise Linux 8

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.