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.

The remote Oracle Linux 6 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2013-0628 advisory.

    [1.2.11.15-12]
    - Resolves: Bug 910994 - PamConfig schema not updated during upgrade
    - Resolves: Bug 910995 - Valgrind reports memleak in modify_update_last_modified_attr
    - Resolves: Bug 910996 - DS returns error 20 when replacing values of a multi-valued attribute  (only when     replication is enabled)
    - Resolves: Bug 911467 - DNA: use event queue for config update only at the start up
    - Resolves: Bug 911468 - Error messages encountered when using POSIX winsync
    - Resolves: Bug 911469 - dse.ldif is 0 length after server kill or machine kill
    - Resolves: Bug 911474 - Invalid chaining config triggers a disk full error and shutdown
    - Resolves: Bug 914305 - ns-slapd segfaults while trying to delete a tombstone entry
    - Resolves: Bug 913228 - unauthenticated denial of service vulnerability in handling of LDAPv3 control     data

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.

A flaw was found in the way LDAPv3 control data was handled by 389 Directory Server. If a malicious user were able to bind to the directory (even anonymously) and send an LDAP request containing crafted LDAPv3 control data, they could cause the server to crash, denying service to the directory. (CVE-2013-0312)

This update also fixes the following bugs :

  - After an upgrade from Scientific Linux 6.3 to version     6.4, the upgrade script did not update the schema file     for the PamConfig object class. Consequently, new     features for PAM such as configuration of multiple     instances and pamFilter attribute could not be used     because of the schema violation. With this update, the     upgrade script updates the schema file for the PamConfig     object class and new features function properly.

  - Previously, the valgrind test suite reported recurring     memory leaks in the modify_update_last_modified_attr()     function. The size of the leaks averaged between 60-80     bytes per modify call. In environments where modify     operations were frequent, this caused significant     problems. Now, memory leaks no longer occur in the     modify_update_last_modified_attr() function.

  - The Directory Server (DS) failed when multi-valued     attributes were replaced. The problem occurred when     replication was enabled, while the server executing the     modification was configured as a single master and there     was at least one replication agreement. Consequently,     the modification requests were refused by the master     server, which returned a code 20 'Type or value exists'     error message. These requests were replacements of     multi-valued attributes, and the error only occurred     when one of the new values matched one of the current     values of the attribute, but had a different letter     case. Now, modification requests function properly and     no longer return code 20 errors.

  - The DNA (distributed numeric assignment) plug-in, under     certain conditions, could log error messages with the     'DB_LOCK_DEADLOCK' error code when attempting to create     an entry with a uidNumber attribute. Now, DNA handles     this case properly and errors no longer occur during     attempts to create entries with uidNumber attributes.

  - Posix Winsync plugin was calling an internal modify     function which was not necessary. The internal modify     call failed and logged an error message     'slapi_modify_internal_set_pb: NULL parameter' which was     not clear. This patch stops calling the internal modify     function if it is not necessary and the cryptic error     message is not observed.

  - Previously, under certain conditions, the dse.ldif file     had 0 bytes after a server termination or when the     machine was powered off. Consequently, after the system     was brought up, a DS or IdM system could be unable to     restart, leading to production server outages. Now, the     server mechanism by which the dse.ldif is written is     more robust, and tries all available backup dse.ldif     files, and outages no longer occur.

  - Due to an incorrect interpretation of an error code, a     directory server considered an invalid chaining     configuration setting as the disk full error and shut     down unexpectedly. Now, a more appropriate error code is     in use and the server no longer shuts down from invalid     chaining configuration settings.

  - While trying to remove a tombstone entry, the ns-slapd     daemon terminated unexpectedly with a segmentation     fault. With this update, removal of tombstone entries no     longer causes crashes.

After installing this update, the 389 server service will be restarted automatically.

Updated 389-ds-base packages that fix one security issue and multiple bugs are now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

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

A flaw was found in the way LDAPv3 control data was handled by 389 Directory Server. If a malicious user were able to bind to the directory (even anonymously) and send an LDAP request containing crafted LDAPv3 control data, they could cause the server to crash, denying service to the directory. (CVE-2013-0312)

The CVE-2013-0312 issue was discovered by Thierry Bordaz of Red Hat.

This update also fixes the following bugs :

* After an upgrade from Red Hat Enterprise Linux 6.3 to version 6.4, the upgrade script did not update the schema file for the PamConfig object class. Consequently, new features for PAM such as configuration of multiple instances and pamFilter attribute could not be used because of the schema violation. With this update, the upgrade script updates the schema file for the PamConfig object class and new features function properly. (BZ#910994)

* Previously, the valgrind test suite reported recurring memory leaks in the modify_update_last_modified_attr() function. The size of the leaks averaged between 60-80 bytes per modify call. In environments where modify operations were frequent, this caused significant problems. Now, memory leaks no longer occur in the modify_update_last_modified_attr() function. (BZ#910995)

* The Directory Server (DS) failed when multi-valued attributes were replaced. The problem occurred when replication was enabled, while the server executing the modification was configured as a single master and there was at least one replication agreement. Consequently, the modification requests were refused by the master server, which returned a code 20 'Type or value exists' error message. These requests were replacements of multi-valued attributes, and the error only occurred when one of the new values matched one of the current values of the attribute, but had a different letter case. Now, modification requests function properly and no longer return code 20 errors. (BZ#910996)

* The DNA (distributed numeric assignment) plug-in, under certain conditions, could log error messages with the 'DB_LOCK_DEADLOCK' error code when attempting to create an entry with a uidNumber attribute.
Now, DNA handles this case properly and errors no longer occur during attempts to create entries with uidNumber attributes. (BZ#911467)

* Posix Winsync plugin was calling an internal modify function which was not necessary. The internal modify call failed and logged an error message 'slapi_modify_internal_set_pb: NULL parameter' which was not clear. This patch stops calling the internal modify function if it is not necessary and the cryptic error message is not observed.
(BZ#911468)

* Previously, under certain conditions, the dse.ldif file had 0 bytes after a server termination or when the machine was powered off.
Consequently, after the system was brought up, a DS or IdM system could be unable to restart, leading to production server outages. Now, the server mechanism by which the dse.ldif is written is more robust, and tries all available backup dse.ldif files, and outages no longer occur. (BZ#911469)

* Due to an incorrect interpretation of an error code, a directory server considered an invalid chaining configuration setting as the disk full error and shut down unexpectedly. Now, a more appropriate error code is in use and the server no longer shuts down from invalid chaining configuration settings. (BZ#911474)

* While trying to remove a tombstone entry, the ns-slapd daemon terminated unexpectedly with a segmentation fault. With this update, removal of tombstone entries no longer causes crashes. (BZ#914305)

All 389-ds-base users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.
After installing this update, the 389 server service will be restarted automatically.

ID	Name	Product	Family	Severity
68788	Oracle Linux 6 : 389-ds-base (ELSA-2013-0628)	Nessus	Oracle Linux Local Security Checks	high
65240	Scientific Linux Security Update : 389-ds-base on SL6.x i386/x86_64 (20130311)	Nessus	Scientific Linux Local Security Checks	medium
65227	CentOS 6 : 389-ds-base (CESA-2013:0628)	Nessus	CentOS Local Security Checks	medium
65206	RHEL 6 : 389-ds-base (RHSA-2013:0628)	Nessus	Red Hat Local Security Checks	medium

Detections

Analytics

CVE-2013-0312

high

Tenable Plugins

high

medium

medium

medium