Skip to content
Fencer Intel
medium 6.2

CVE-2011-0532 json

The (1) backup and restore scripts, (2) main initialization script, and (3) ldap-agent script in 389 Directory Server 1.2.x (aka Red Hat Di…

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

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

Summary

The (1) backup and restore scripts, (2) main initialization script, and (3) ldap-agent script in 389 Directory Server 1.2.x (aka Red Hat Directory Server 8.2.x) place a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.

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-0532 updated cvss 6.2

Server: use of insecure LD_LIBRARY_PATH settings

  • 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

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

CVSS scores

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

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.