Important: JBoss Enterprise Application Platform 4.3.0 CP10 security update
|Last updated on:||2013-02-11|
|Affected Products:||JBoss Enterprise Application Platform 4.3.0 EL5|
An update for JBoss Enterprise Application Platform 4.3.0 CP10 which fixes
one security issue is now available from the Red Hat Customer Portal.
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.
JBoss Enterprise Application Platform is a platform for Java applications,
which integrates the JBoss Application Server with JBoss Hibernate and
When using LDAP authentication with the provided LDAP login modules
(LdapLoginModule/LdapExtLoginModule), empty passwords were allowed by
default. An attacker could use this flaw to bypass intended authentication
by providing an empty password for a valid username, as the LDAP server may
recognize this as an 'unauthenticated authentication' (RFC 4513). This
update sets the allowEmptyPasswords option for the LDAP login modules to
false if the option is not already configured. (CVE-2012-5629)
Warning: Before applying this update, back up your existing JBoss
Enterprise Application Platform installation (including all applications
and configuration files).
All users of JBoss Enterprise Application Platform 4.3.0 CP10 as provided
from the Red Hat Customer Portal are advised to apply this update.
log in to download the update). Before applying the update, back up your
existing JBoss Enterprise Application Platform installation (including all
applications and configuration files).
The JBoss server process must be restarted for this update to take effect.
|(The unlinked packages above are only available from the Red Hat Network)|
Bugs fixed (see bugzilla for more information)
885569 - CVE-2012-5629 JBoss: allows empty password to authenticate against LDAP
These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from: