Moderate CentOS 389-ds-base Update
|389-ds-base-18.104.22.168-11.el6.i686.rpm, 389-ds-base-22.214.171.124-11.el6.src.rpm, 389-ds-base-126.96.36.199-11.el6.x86_64.rpm, 389-ds-base-devel-188.8.131.52-11.el6.i686.rpm, 389-ds-base-devel-184.108.40.206-11.el6.x86_64.rpm, 389-ds-base-libs-220.127.116.11-11.el6.i686.rpm, 389-ds-base-libs-18.104.22.168-11.el6.x86_64.rpm|
|rhn.redhat.com, lists.centos.org, lists.centos.org|
Updated 389-ds-base packages that fix one security issue, numerous bugs,
and add various enhancements are now available for Red Hat Enterprise
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-ds-base packages provide 389 Directory Server, which is an LDAPv3
compliant server. The base packages include the Lightweight Directory
Access Protocol (LDAP) server and command-line utilities for server
A flaw was found in the way 389 Directory Server enforced ACLs after
performing an LDAP modify relative distinguished name (modrdn) operation.
After modrdn was used to move part of a tree, the ACLs defined on the moved
(Distinguished Name) were not properly enforced until the server was
restarted. This could allow LDAP users to access information that should be
restricted by the defined ACLs. (CVE-2012-4450)
This issue was discovered by Noriko Hosoi of Red Hat.
These updated 389-ds-base packages 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.4
Technical Notes, linked to in the References, for information on the most
significant of these changes.
All users of 389-ds-base are advised to upgrade to these updated packages,
which correct this issue and provide numerous bug fixes and enhancements.
After installing this update, the 389 server service will be restarted
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