CentOS Update for 389-ds-base CESA-2013:0742 centos6

Published: 2013-04-19 04:35:37
CVE Author: NIST National Vulnerability Database

Affected Versions:
389-ds-base on CentOS 6

Recommendations:
Please install the updated Linux Distribution Packages.

Technical Details:
The 389 Directory Server is an LDAPv3 compliant server. The base Linux Distribution Packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration. It was found that the 389 Directory Server did not properly restrict access to entries when the 'nsslapd-allow-anonymous-access' configuration setting was set to 'rootdse'. An anonymous user could connect to the LDAP database and, if the search scope is set to BASE, obtain access to information outside of the rootDSE. (CVE-2013-1897) This issue was discovered by Martin Kosek of Red Hat. This update also fixes the following bugs: * Previously, the schema-reload plug-in was not thread-safe. Consequently, executing the schema-reload.pl script under heavy load could have caused the ns-slapd process to terminate unexpectedly with a segmentation fault. Currently, the schema-reload plug-in is re-designed so that it is thread-safe, and the schema-reload.pl script can be executed along with other LDAP operations. (BZ#929107) * An out of scope problem for a local variable, in some cases, caused the modrdn operation to terminate unexpectedly with a segmentation fault. This update declares the local variable at the proper place of the function so it does not go out of scope, and the modrdn operation no longer crashes. (BZ#929111) * A task manually constructed an exact value to be removed from the configuration if the 'replica-force-cleaning' option was used. Consequently, the task configuration was not cleaned up, and every time the server was restarted, the task behaved in the described manner. This update searches the configuration for the exact value to delete, instead of manually building the value, and the task does not restart when the server is restarted. (BZ#929114) * Previously, a NULL pointer dereference could have occurred when attempting to get effective rights on an entry that did not exist, leading to an unexpected termination due to a segmentation fault. This update checks for NULL entry pointers and returns the appropriate error. Now, attempts to get effective rights on an entry that does not exist no longer causes crashes, and the server returns the appropriate error message. (BZ#929115) * A problem in the lock timing in the DNA plug-in caused a deadlock if the DNA operation was executed with other plug-ins. This update moves the release timing of the problematic lock, and the DNA plug-in does not cause the deadlock. (BZ#929196) All 389-ds-base users are advised to upgrade to these updated Linux Distribution Packages, which contain backported patches to correct these issues. After installing this update, the 389 server service will be restarted automatically.

CVSS Base Vector:
AV:N/AC:H/Au:N/C:P/I:N/A:N

Detection Type:
Linux Distribution Package

Solution Type:
Vendor Patch

Summary:
The remote host is missing an update for the '389-ds-base' Linux Distribution Package(s) announced via the referenced advisory.

NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)

https://nvd.nist.gov/vuln/detail/CVE-2013-1897

References:

http://lists.centos.org/pipermail/centos-announce/2013-April/019689.html

Severity
Low
CVSS Score
2.6
Published
2013-04-19
Modified
2019-03-15
Category
CentOS Local Security Checks

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities