389 Directory Server vulnerabilitiesRanked by how likely they are to be used.
389 Directory Server is made by Fedoraproject. We track 39 published vulnerabilities in it, across 185 versions. None of them is on the list of flaws known to be exploited today. If you run 389 Directory Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which 389 Directory Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of 389 Directory Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which 389 Directory Server flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.2%CVE-2019-3883High
In 389-ds-base up to version 1.4.1.2, requests are handled by workers threads.
- 6.3%CVE-2018-14648High
A flaw was found in 389 Directory Server.
- 4.6%CVE-2018-1054High
An out-of-bounds memory read flaw was found in the way 389-ds-base handled certain LDAP search filters, affecting all versions including 1.4.x.
- 4.1%CVE-2018-1089High
389-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, possibly leading to buffer overflows.
- 4.0%CVE-2016-0741High
slapd/connection.c in 389 Directory Server (formerly Fedora Directory Server) 1.3.4.x before 1.3.4.7 allows remote attackers to cause a denial of service (infinite loop and connection blocking) by leveraging an...
- 3.9%CVE-2017-15134High
A stack buffer overflow flaw was found in the way 389-ds-base 1.3.6.x before 1.3.6.13, 1.3.7.x before 1.3.7.9, 1.4.x before 1.4.0.5 handled certain LDAP search filters.
- 3.8%CVE-2017-15135High
It 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 during the authentication process.
- 2.8%CVE-2017-2591High
389-ds-base before version 1.3.6 is vulnerable to an improperly NULL terminated array in the uniqueness_entry_to_config() function in the "attribute uniqueness" plugin of 389 Directory Server.
- 2.7%CVE-2013-0312Medium
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.
- 2.6%CVE-2018-14638High
A flaw was found in 389-ds-base before version 1.3.8.4-13.
Running 389 Directory Server? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In 389-ds-base up to version 1.4.1.2, requests are handled by workers threads. Each sockets will be waited by the worker for at most 'ioblocktimeout' seconds. However this timeout applies only for un-encrypted requests. Connections using SSL/TLS are not taking this timeout into account during reads, and may hang longer.An unauthenticated attacker could repeatedly create hanging LDAP requests to hang all the workers, resulting in a Denial of Service.
- Matched to
- 389 Directory Server on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 39 published vulnerabilities listed under the name 389 Directory Server, across 185 versions.
None of 389 Directory Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track 389 Directory Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.