A flaw was found in 389-ds-base before version 1.3.8.4-13.
Noroxi assessment
Priority: Monitor (action score 31/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: 2.6% (FIRST EPSS); higher than 85.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: 389-ds-base (Debian:12) 1.4.0.18-1; 389-ds (openSUSE:Tumbleweed) 2.0.10~git0.21dd2802c-1.1; 389-ds-base (Red Hat:enterprise_linux:7::client) 0:1.3.7.5-28.el7_5.
Low priority for now. Upgrade to 389-ds-base (Debian:12) 1.4.0.18-1; 389-ds (openSUSE:Tumbleweed) 2.0.10~git0.21dd2802c-1.1; 389-ds-base (Red Hat:enterprise_linux:7::client) 0:1.3.7.5-28.el7_5 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
A flaw was found in 389-ds-base before version 1.3.8.4-13. The process ns-slapd crashes in delete_passwdPolicy function when persistent search connections are terminated unexpectedly leading to remote denial of service.
- Published
- Sep 14, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-400
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
CNA vs NVD score
- NVD
- 7.5
- CNA · redhat
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 | enterprise linux aus | cpe:2.3:o:redhat:enterprise_linux_aus |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux server eus | cpe:2.3:o:redhat:enterprise_linux_server_eus |
| redhat | enterprise linux server tus | cpe:2.3:o:redhat:enterprise_linux_server_tus |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject 389 directory serverbefore 1.3.8.4
- redhat enterprise linux aus7.6
- redhat enterprise linux desktop7.0
- redhat enterprise linux server7.0
- redhat enterprise linux server eus7.5
- redhat enterprise linux server eus7.6
- redhat enterprise linux server tus7.6
- redhat enterprise linux workstation7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Fedora Project 389-ds-base
- 1.3.8.4-13affected
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.4.0.18-1 | 1.4.0.18-1 |
| openSUSE:Tumbleweed | 389-ds | before 2.0.10~git0.21dd2802c-1.1 | 2.0.10~git0.21dd2802c-1.1 |
| Red Hat:enterprise_linux:7::client | 389-ds-base | before 0:1.3.7.5-28.el7_5 | 0:1.3.7.5-28.el7_5 |
| Red Hat:enterprise_linux:7::client | 389-ds-base-debuginfo | before 0:1.3.7.5-28.el7_5 | 0:1.3.7.5-28.el7_5 |
| Red Hat:enterprise_linux:7::client | 389-ds-base-devel | before 0:1.3.7.5-28.el7_5 | 0:1.3.7.5-28.el7_5 |
| Red Hat:enterprise_linux:7::client | 389-ds-base-libs | before 0:1.3.7.5-28.el7_5 | 0:1.3.7.5-28.el7_5 |
| Red Hat:enterprise_linux:7::client | 389-ds-base-snmp | before 0:1.3.7.5-28.el7_5 | 0:1.3.7.5-28.el7_5 |
| SUSE:Linux Enterprise Module for Server Applications 15 | 389-ds | before 1.4.0.26~git0.8a2d3de6f-4.14.1 | 1.4.0.26~git0.8a2d3de6f-4.14.1 |
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
- CVE-2018-14648A flaw was found in 389 Directory Server.32Monitor
- 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
- CVE-2018-1089389-ds-base before versions 1.4.0.9, 1.3.8.1, 1.3.6.15 did not properly handle long search filters with characters needing escapes, possibly31Monitor
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.4.0.18-1 · Debian:12 | Package registry (OSV) |
| opensuse:389-ds | 2.0.10~git0.21dd2802c-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:389-ds-base | 0:1.3.7.5-28.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:389-ds-base-debuginfo | 0:1.3.7.5-28.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:389-ds-base-devel | 0:1.3.7.5-28.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:389-ds-base-libs | 0:1.3.7.5-28.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:389-ds-base-snmp | 0:1.3.7.5-28.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:389-ds | 1.4.0.26~git0.8a2d3de6f-4.14.1 · SUSE:Linux Enterprise Module for Server Applications 15 | 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.