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)

The following packages have been upgraded to a newer upstream version:
389 -ds-base (1.3.5.10).

Security Fix(es) :

  - It was found that 389 Directory Server was vulnerable to     a flaw in which the default ACI (Access Control     Instructions) could be read by an anonymous user. This     could lead to leakage of sensitive information.
    (CVE-2016-5416)

  - An information disclosure flaw was found in 389     Directory Server. A user with no access to objects in     certain LDAP sub-tree could send LDAP ADD operations     with a specific object name. The error message returned     to the user was different based on whether the target     object existed or not. (CVE-2016-4992)

  - It was found that 389 Directory Server was vulnerable to     a remote password disclosure via timing attack. A remote     attacker could possibly use this flaw to retrieve     directory server password after many tries.
    (CVE-2016-5405)

The CVE-2016-5416 issue was discovered by Viktor Ashirov (Red Hat);
the CVE-2016-4992 issue was discovered by Petr Spacek (Red Hat) and Martin Basti (Red Hat); and the CVE-2016-5405 issue was discovered by William Brown (Red Hat).

Additional Changes :

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

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) :

* It was found that 389 Directory Server was vulnerable to a flaw in which the default ACI (Access Control Instructions) could be read by an anonymous user. This could lead to leakage of sensitive information. (CVE-2016-5416)

* An information disclosure flaw was found in 389 Directory Server. A user with no access to objects in certain LDAP sub-tree could send LDAP ADD operations with a specific object name. The error message returned to the user was different based on whether the target object existed or not. (CVE-2016-4992)

* It was found that 389 Directory Server was vulnerable to a remote password disclosure via timing attack. A remote attacker could possibly use this flaw to retrieve directory server password after many tries. (CVE-2016-5405)

The CVE-2016-5416 issue was discovered by Viktor Ashirov (Red Hat);
the CVE-2016-4992 issue was discovered by Petr Spacek (Red Hat) and Martin Basti (Red Hat); and the CVE-2016-5405 issue was discovered by William Brown (Red Hat).

Bug Fix(es) :

* Previously, a bug in the changelog iterator buffer caused it to point to an incorrect position when reloading the buffer. This caused replication to skip parts of the changelog, and consequently some changes were not replicated. This bug has been fixed, and replication data loss due to an incorrectly reloaded changelog buffer no longer occurs. (BZ#1354331)

* Previously, if internal modifications were generated on a consumer (for example by the Account Policy plug-in) and additional changes to the same attributes were received from replication, a bug caused Directory Server to accumulate state information on the consumer. The bug has been fixed by making sure that replace operations are only applied if they are newer than existing attribute deletion change sequence numbers (CSNs), and state information no longer accumulates in this situation. (BZ#1379599)

Enhancement(s) :

* In a multi-master replication environment where multiple masters receive updates at the same time, it was previously possible for a single master to obtain exclusive access to a replica and hold it for a very long time due to problems such as a slow network connection.
During this time, other masters were blocked from accessing the same replica, which considerably slowed down the replication process. This update adds a new configuration attribute, 'nsds5ReplicaReleaseTimeout', which can be used to specify a timeout in seconds. After the specified timeout period passes, the master releases the replica, allowing other masters to access it and send their updates. (BZ#1358390)

Security Fix(es) :

  - It was found that 389 Directory Server was vulnerable to     a flaw in which the default ACI (Access Control     Instructions) could be read by an anonymous user. This     could lead to leakage of sensitive information.
    (CVE-2016-5416)

  - An information disclosure flaw was found in 389     Directory Server. A user with no access to objects in     certain LDAP sub-tree could send LDAP ADD operations     with a specific object name. The error message returned     to the user was different based on whether the target     object existed or not. (CVE-2016-4992)

  - It was found that 389 Directory Server was vulnerable to     a remote password disclosure via timing attack. A remote     attacker could possibly use this flaw to retrieve     directory server password after many tries.
    (CVE-2016-5405)

Bug Fix(es) :

  - Previously, a bug in the changelog iterator buffer     caused it to point to an incorrect position when     reloading the buffer. This caused replication to skip     parts of the changelog, and consequently some changes     were not replicated. This bug has been fixed, and     replication data loss due to an incorrectly reloaded     changelog buffer no longer occurs.

  - Previously, if internal modifications were generated on     a consumer (for example by the Account Policy plug-in)     and additional changes to the same attributes were     received from replication, a bug caused Directory Server     to accumulate state information on the consumer. The bug     has been fixed by making sure that replace operations     are only applied if they are newer than existing     attribute deletion change sequence numbers (CSNs), and     state information no longer accumulates in this     situation.

Enhancement(s) :

  - In a multi-master replication environment where multiple     masters receive updates at the same time, it was     previously possible for a single master to obtain     exclusive access to a replica and hold it for a very     long time due to problems such as a slow network     connection. During this time, other masters were blocked     from accessing the same replica, which considerably     slowed down the replication process. This update adds a     new configuration attribute,     'nsds5ReplicaReleaseTimeout', which can be used to     specify a timeout in seconds. After the specified     timeout period passes, the master releases the replica,     allowing other masters to access it and send their     updates.

ID	名稱	產品	系列	已發布	已更新	嚴重性
105366	openSUSE Security Update : 389-ds (openSUSE-2017-1396)	Nessus	SuSE Local Security Checks	2017/12/19	2025/11/11	critical
95832	Scientific Linux Security Update : 389-ds-base on SL7.x x86_64 (20161103)	Nessus	Scientific Linux Local Security Checks	2016/12/15	2026/1/14	critical
94979	CentOS 6 : 389-ds-base (CESA-2016:2765)	Nessus	CentOS Local Security Checks	2016/11/21	2026/1/16	critical
95049	Scientific Linux Security Update : 389-ds-base on SL6.x i386/x86_64 (20161115)	Nessus	Scientific Linux Local Security Checks	2016/11/22	2026/1/16	critical

偵測

搜尋 Plugin

critical

critical

critical

critical