Skip to content
Noroxi
CVE-2013-2219· NVD / CVE Program· CNA redhat

The Red Hat Directory Server before 8.2.11-13 and 389 Directory Server do not properly restrict access to entity attributes, which allows re

The Red Hat Directory Server before 8.2.11-13 and 389 Directory Server do not properly restrict access to entity attributes, which allows remote authenticated users to obtain sensitive information via a search query for the attribute.

MediumCVSS 4.0 · v2.0—No exploit Fix available
Published
Jul 31, 2013
Updated
Jun 16, 2026
EPSS
1.8% · 77th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
16 / 40 · 4.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

Affected systems

VendorProduct
fedoraproject389 directory server
redhatdirectory server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject 389 directory serverall versions
  • redhat directory serverup to 8.2 inclusive
  • redhat directory server7.1
  • redhat directory server8.0
  • redhat directory server8.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12389-ds-basebefore 1.3.2.9-11.3.2.9-1
Red Hat:directory_server:8::el5redhat-ds-basebefore 0:8.2.11-13.el5dsrv0:8.2.11-13.el5dsrv
Red Hat:directory_server:8::el5redhat-ds-base-debuginfobefore 0:8.2.11-13.el5dsrv0:8.2.11-13.el5dsrv
Red Hat:directory_server:8::el5redhat-ds-base-develbefore 0:8.2.11-13.el5dsrv0:8.2.11-13.el5dsrv
Red Hat:enterprise_linux:6::client389-ds-basebefore 0:1.2.11.15-20.el6_40:1.2.11.15-20.el6_4
Red Hat:enterprise_linux:6::client389-ds-base-debuginfobefore 0:1.2.11.15-20.el6_40:1.2.11.15-20.el6_4
Red Hat:enterprise_linux:6::client389-ds-base-develbefore 0:1.2.11.15-20.el6_40:1.2.11.15-20.el6_4
Red Hat:enterprise_linux:6::client389-ds-base-libsbefore 0:1.2.11.15-20.el6_40:1.2.11.15-20.el6_4

Other highest-scoring records for the same primary product.

  • CVE-2017-7551389-ds-base version before 1.3.5.19 and 1.3.6.7 are vulnerable to password brute-force attacks during account lockout due to different retur
    39Monitor
  • CVE-2017-15135It was found that 389-ds-base since 1.3.6.1 up to and including 1.4.0.3 did not always handle internal hash comparison operations correctly
    33Monitor
  • CVE-2019-3883In 389-ds-base up to version 1.4.1.2, requests are handled by workers threads.
    32Monitor
  • CVE-2018-14648A flaw was found in 389 Directory Server.
    32Monitor
  • CVE-2018-14638A flaw was found in 389-ds-base before version 1.3.8.4-13.
    31Monitor
  • CVE-2018-14624A vulnerability was discovered in 389-ds-base through versions 1.3.7.10, 1.3.8.8 and 1.4.0.16.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:389-ds-base1.3.2.9-1 · Debian:12Package registry (OSV)
red hat:389-ds-base0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-debuginfo0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-devel0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-libs0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:redhat-ds-base0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5Package registry (OSV)
red hat:redhat-ds-base-debuginfo0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5Package registry (OSV)
red hat:redhat-ds-base-devel0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:S/C:P/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records