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
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: 389-ds-base (Debian:12) 1.3.2.9-1; redhat-ds-base (Red Hat:directory_server:8::el5) 0:8.2.11-13.el5dsrv; redhat-ds-base-debuginfo (Red Hat:directory_server:8::el5) 0:8.2.11-13.el5dsrv.
Low priority for now. Upgrade to 389-ds-base (Debian:12) 1.3.2.9-1; redhat-ds-base (Red Hat:directory_server:8::el5) 0:8.2.11-13.el5dsrv; redhat-ds-base-debuginfo (Red Hat:directory_server:8::el5) 0:8.2.11-13.el5dsrv or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 31, 2013
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-264
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| fedoraproject | 389 directory server | cpe:2.3:a:fedoraproject:389_directory_server |
| redhat | directory server | cpe:2.3:a:redhat:directory_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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | 389-ds-base | before 1.3.2.9-1 | 1.3.2.9-1 |
| Red Hat:directory_server:8::el5 | redhat-ds-base | before 0:8.2.11-13.el5dsrv | 0:8.2.11-13.el5dsrv |
| Red Hat:directory_server:8::el5 | redhat-ds-base-debuginfo | before 0:8.2.11-13.el5dsrv | 0:8.2.11-13.el5dsrv |
| Red Hat:directory_server:8::el5 | redhat-ds-base-devel | before 0:8.2.11-13.el5dsrv | 0:8.2.11-13.el5dsrv |
| Red Hat:enterprise_linux:6::client | 389-ds-base | before 0:1.2.11.15-20.el6_4 | 0:1.2.11.15-20.el6_4 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-debuginfo | before 0:1.2.11.15-20.el6_4 | 0:1.2.11.15-20.el6_4 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-devel | before 0:1.2.11.15-20.el6_4 | 0:1.2.11.15-20.el6_4 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-libs | before 0:1.2.11.15-20.el6_4 | 0:1.2.11.15-20.el6_4 |
Same product
fedoraproject: all recordsOther 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 retur39Monitor
- 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
Published before and after this one in the same product
- ← EarlierCVE-2013-0312Mar 13, 2013 · 389 Directory Server before 1.3.0.4 allows remote attackers to cause a denial of service (crash) via a zero length LDAP control sequence.21Monitor
- ← EarlierCVE-2013-1897May 13, 2013 · The do_search function in ldap/servers/slapd/search.c in 389 Directory Server 1.2.x before 1.2.11.20 and 1.3.x before 1.3.0.5 does not prope11Monitor
- Later →CVE-2013-4283Sep 10, 2013 · ns-slapd in 389 Directory Server before 1.3.0.8 allows remote attackers to cause a denial of service (server crash) via a crafted Distinguis21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:389-ds-base | 1.3.2.9-1 · Debian:12 | Package registry (OSV) |
| red hat:389-ds-base | 0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-debuginfo | 0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-devel | 0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-libs | 0:1.2.11.15-20.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:redhat-ds-base | 0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5 | Package registry (OSV) |
| red hat:redhat-ds-base-debuginfo | 0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5 | Package registry (OSV) |
| red hat:redhat-ds-base-devel | 0:8.2.11-13.el5dsrv · Red Hat:directory_server:8::el5 | Package 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.
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.
Credits
All researchersFinders, 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
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS 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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.