Low CentOS 389-ds-base Update
|389-ds-base-22.214.171.124-15.el6.i686.rpm, 389-ds-base-126.96.36.199-15.el6.src.rpm, 389-ds-base-188.8.131.52-15.el6.x86_64.rpm, 389-ds-base-devel-184.108.40.206-15.el6.i686.rpm, 389-ds-base-devel-220.127.116.11-15.el6.x86_64.rpm, 389-ds-base-libs-18.104.22.168-15.el6.i686.rpm, 389-ds-base-libs-22.214.171.124-15.el6.x86_64.rpm|
Updated 389-ds-base packages that fix one security issue, several bugs, and
add various enhancements are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having low
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 the 389 Directory Server daemon (ns-slapd)
handled access control instructions (ACIs) using certificate groups. If an
LDAP user that had a certificate group defined attempted to bind to the
directory server, it would cause ns-slapd to enter an infinite loop and
consume an excessive amount of CPU time. (CVE-2012-0833)
Red Hat would like to thank Graham Leggett for reporting this issue.
These updated 389-ds-base packages also include numerous bug fixes and
enhancements. Space precludes documenting all of these changes in this
advisory. Users are directed to the Red Hat Enterprise Linux 6.3 Technical
Notes for information on the most significant of these changes.
Users are advised to upgrade to these updated 389-ds-base packages, which
resolve these issues and add these enhancements. After installing this
update, the 389 server service will be restarted automatically.
Please see https://www.redhat.com/footer/terms-of-use.html
Am I vulnerable?
The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.
Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.Sign up for monitoring
Affected package information