Important CentOS ipa Update
|ipa-2.2.0-17.el6_3.1.src.rpm, ipa-admintools-2.2.0-17.el6_3.1.i686.rpm, ipa-admintools-2.2.0-17.el6_3.1.x86_64.rpm, ipa-client-2.2.0-17.el6_3.1.i686.rpm, ipa-client-2.2.0-17.el6_3.1.x86_64.rpm, ipa-python-2.2.0-17.el6_3.1.i686.rpm, ipa-python-2.2.0-17.el6_3.1.x86_64.rpm, ipa-server-2.2.0-17.el6_3.1.i686.rpm, ipa-server-2.2.0-17.el6_3.1.x86_64.rpm, ipa-server-selinux-2.2.0-17.el6_3.1.i686.rpm, ipa-server-selinux-2.2.0-17.el6_3.1.x86_64.rpm|
Updated ipa packages that fix one security issue are now available for
Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having
important 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.
Red Hat Identity Management is a centralized authentication, identity
management and authorization solution for both traditional and cloud-based
A weakness was found in the way IPA clients communicated with IPA servers
when initially attempting to join IPA domains. As there was no secure way
to provide the IPA server's Certificate Authority (CA) certificate to the
client during a join, the IPA client enrollment process was susceptible to
man-in-the-middle attacks. This flaw could allow an attacker to obtain
access to the IPA server using the credentials provided by an IPA client,
including administrative access to the entire domain if the join was
performed using an administrator's credentials. (CVE-2012-5484)
Note: This weakness was only exposed during the initial client join to the
realm, because the IPA client did not yet have the CA certificate of the
server. Once an IPA client has joined the realm and has obtained the CA
certificate of the IPA server, all further communication is secure. If a
client were using the OTP (one-time password) method to join to the realm,
an attacker could only obtain unprivileged access to the server (enough to
only join the realm).
Red Hat would like to thank Petr Menšík for reporting this issue.
This update must be installed on both the IPA client and IPA server. When
this update has been applied to the client but not the server,
ipa-client-install, in unattended mode, will fail if you do not have the
correct CA certificate locally, noting that you must use the "--force"
option to insecurely obtain the certificate. In interactive mode, the
certificate will try to be obtained securely from LDAP. If this fails, you
will be prompted to insecurely download the certificate via HTTP. In the
same situation when using OTP, LDAP will not be queried and you will be
prompted to insecurely download the certificate via HTTP.
Users of ipa are advised to upgrade to these updated packages, which
correct this issue. After installing the update, changes in LDAP are
handled by ipa-ldap-updater automatically and are effective immediately.
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