Skip to content
Fencer Intel
high 7.5

CVE-2011-0019 json

slapd (aka ns-slapd) in 389 Directory Server 1.2.7.5 (aka Red Hat Directory Server 8.2.x or dirsrv) does not properly handle simple paged r…

published 2011-02-23 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0045

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

slapd (aka ns-slapd) in 389 Directory Server 1.2.7.5 (aka Red Hat Directory Server 8.2.x or dirsrv) does not properly handle simple paged result searches, which allows remote attackers to cause a denial of service (daemon crash) or possibly have unspecified other impact via multiple search requests.

Patch / fix

  • redhat-ds-base directory server 8 8.2.4-1.el5dsrv
  • redhat-ds-admin directory server 8 8.2.1-1.el5dsrv

red hat advisories RHSA-2011:0293

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-2011-0019 updated cvss 3.3

Server: crash with multiple simple paged result searches

  • Red Hat Directory Server 8 (for RHEL 5 Server) redhat-ds-base 8.2.4-1.el5dsrv, redhat-ds-admin 8.2.1-1.el5dsrv
    fixed: vendor fix RHSA-2011:0293
  • Red Hat Directory Server 8.0 (for AS v. 4) redhat-ds-base 8.2.4-1.el4dsrv, redhat-ds-admin 8.2.1-1.el4dsrv Red Hat Directory Server 8.0 (for ES v. 4) redhat-ds-base 8.2.4-1.el4dsrv, redhat-ds-admin 8.2.1-1.el4dsrv
    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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

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.