This update for 389-ds fixes the following issues :

  - CVE-2017-7551: 389-ds-base: Password brute-force     possible for locked account due to different return     codes (bsc#1051997)

  - CVE-2016-4992: 389-ds: Information disclosure via     repeated use of LDAP ADD operation (bsc#997256)

  - CVE-2016-5405: 389-ds: Password verification vulnerable     to timing attack (bsc#1007004)

  - CVE-2017-2591: 389-ds-base: Heap buffer overflow in     uiduniq.c (bsc#1020670)

  - CVE-2017-2668 389-ds Remote crash via crafted LDAP     messages (bsc#1069067)

  - CVE-2016-0741: 389-ds: worker threads do not detect     abnormally closed connections causing DoS (bsc#1069074)

According to the versions of the 389-ds-base packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - 389-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 return codes returned     on password attempts.(CVE-2017-7551)

  - 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.(CVE-2019-3883)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Oracle Linux 7 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2017-2569 advisory.

    [1.3.6.19-1]
    - Bump version to 1.3.6.19-1
    - Remove old mozldap and db4 requirements
    - Resolves: Bug 1483865 - Crash while binding to a server during replication online init

    [1.3.6.1-18]
    - Bump version to 1.3.6.1-18
    - Require srvcore 4.1.3
    - Resolves: Bug 1479757 - dse.ldif and fsync
    - Resolves: Bug 1479755 - backup fails if changelog is enabled
    - Resolves: Bug 1479756 - Locked account provides different return code if password is correct

    [1.3.6.1-17]
    - Bump version to 1.3.6.1-17
    - Resolves: Bug 1476161 - replication halt - pending list first CSN not committed, pending list increasing
    - Resolves: Bug 1476162 - Change the retrochangelog default cache size

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 389-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 return codes returned on password attempts. (CVE-2017-7551)

Note that Nessus relies on the presence of the package as reported by the vendor.

Password brute-force possible for locked account due to different return codes :

A flaw was found in the way 389-ds-base handled authentication attempts against locked accounts. A remote attacker could potentially use this flaw to continue password brute-forcing attacks against LDAP accounts, thereby bypassing the protection offered by the directory server's password lockout policy. (CVE-2017-7551)

Security Fix(es) :

  - A flaw was found in the way 389-ds-base handled     authentication attempts against locked accounts. A     remote attacker could potentially use this flaw to     continue password brute-forcing attacks against LDAP     accounts, thereby bypassing the protection offered by     the directory server's password lockout policy.
    (CVE-2017-7551)

Bug Fix(es) :

  - In a multi-replication environments, if operations in     one back end triggered updates in another back end, the     Replica Update Vector (RUV) of the back end was     incorrect and replication failed. This fix enables     Directory Server to handle Change Sequence Number (CSN)     pending lists across multiple back ends. As a result,     replication works correctly.

  - Due to a low default entry cache size value, the     Directory Server database had to resolve many deadlocks     during resource-intensive tasks. In certain situations,     this could result in a 'DB PANIC' error and the server     no longer responded to requests. After the server was     restarted, Directory Server started with a delay to     recover the database. However, this recovery could fail,     and the database could corrupt. This patch increases the     default entry cache size in the nsslapd-cachememsize     parameter to 200 MB. As a result, out-of-lock situations     or 'DB PANIC' errors no longer occur in the mentioned     scenario.

  - Previously, if replication was enabled and a changelog     file existed, performing a backup on this master server     failed. This update sets the internal options for     correctly copying a file. As a result, creating a backup     now succeeds in the mentioned scenario.

  - In certain situations, if the server was previously     abruptly shut down, the     /etc/dirsrv/<instance_name>/dse.ldif configuration file     became corrupted. As a consequence, Directory Server     failed to start. With this patch, the server now calls     the fsync() function before shutting down to force the     file system to write any changes to the disk. As a     result, the configuration no longer becomes corrupted,     regardless how the server gets stopped.

An update for 389-ds-base is now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

389 Directory Server is an LDAP version 3 (LDAPv3) compliant server.
The base packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration.

Security Fix(es) :

* A flaw was found in the way 389-ds-base handled authentication attempts against locked accounts. A remote attacker could potentially use this flaw to continue password brute-forcing attacks against LDAP accounts, thereby bypassing the protection offered by the directory server's password lockout policy. (CVE-2017-7551)

Bug Fix(es) :

* In a multi-replication environments, if operations in one back end triggered updates in another back end, the Replica Update Vector (RUV) of the back end was incorrect and replication failed. This fix enables Directory Server to handle Change Sequence Number (CSN) pending lists across multiple back ends. As a result, replication works correctly.
(BZ# 1476161)

* Due to a low default entry cache size value, the Directory Server database had to resolve many deadlocks during resource-intensive tasks. In certain situations, this could result in a 'DB PANIC' error and the server no longer responded to requests. After the server was restarted, Directory Server started with a delay to recover the database. However, this recovery could fail, and the database could corrupt. This patch increases the default entry cache size in the nsslapd-cachememsize parameter to 200 MB. As a result, out-of-lock situations or 'DB PANIC' errors no longer occur in the mentioned scenario. (BZ#1476162)

* Previously, if replication was enabled and a changelog file existed, performing a backup on this master server failed. This update sets the internal options for correctly copying a file. As a result, creating a backup now succeeds in the mentioned scenario. (BZ#1479755)

* In certain situations, if the server was previously abruptly shut down, the /etc/dirsrv//dse.ldif configuration file became corrupted.
As a consequence, Directory Server failed to start. With this patch, the server now calls the fsync() function before shutting down to force the file system to write any changes to the disk. As a result, the configuration no longer becomes corrupted, regardless how the server gets stopped. (BZ# 1479757)

ID	Name	Product	Family	Published	Updated	Severity
105366	openSUSE Security Update : 389-ds (openSUSE-2017-1396)	Nessus	SuSE Local Security Checks	12/19/2017	1/19/2021	critical
131861	EulerOS 2.0 SP2 : 389-ds-base (EulerOS-SA-2019-2369)	Nessus	Huawei Local Security Checks	12/10/2019	4/4/2024	critical
102970	Oracle Linux 7 : 389-ds-base (ELSA-2017-2569)	Nessus	Oracle Linux Local Security Checks	9/6/2017	10/22/2024	critical
221241	Linux Distros Unpatched Vulnerability : CVE-2017-7551	Nessus	Misc.	3/4/2025	3/4/2025	critical
103602	Amazon Linux AMI : 389-ds-base (ALAS-2017-905)	Nessus	Amazon Linux Local Security Checks	10/3/2017	4/18/2018	critical
102972	Scientific Linux Security Update : 389-ds-base on SL7.x x86_64 (20170905)	Nessus	Scientific Linux Local Security Checks	9/6/2017	1/14/2021	critical
103038	RHEL 7 : 389-ds-base (RHSA-2017:2569)	Nessus	Red Hat Local Security Checks	9/8/2017	10/24/2019	critical
103035	CentOS 7 : 389-ds-base (CESA-2017:2569)	Nessus	CentOS Local Security Checks	9/8/2017	1/4/2021	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical