Issued:

2014-09-04

Updated:

2014-09-04

RHSA-2014:1162 - Important: Red Hat JBoss Enterprise Application Platform 6.3.0 security update

Synopsis

Important: Red Hat JBoss Enterprise Application Platform 6.3.0 security update

Type/Severity

Security Advisory Important

Topic

Updated Red Hat JBoss Enterprise Application Platform 6.3.0 packages that fix two security issues are now available for Red Hat Enterprise Linux 5, 6, and 7.

Red Hat Product Security has rated this update as having Important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Description

Red Hat JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7.

It was found that the fix for CVE-2012-5783 was incomplete: the code added to check that the server host name matches the domain name in a subject's Common Name (CN) field in X.509 certificates was flawed. A man-in-the-middle attacker could use this flaw to spoof an SSL server using a specially crafted X.509 certificate. (CVE-2012-6153)

It was discovered that the HttpClient incorrectly extracted host name from an X.509 certificate subject's Common Name (CN) field. A man-in-the-middle attacker could use this flaw to spoof an SSL server using a specially crafted X.509 certificate. (CVE-2014-3577)

The CVE-2012-6153 issue was discovered by Florian Weimer of Red Hat Product Security.

For additional information on these flaws, refer to the Knowledgebase article in the References section.

All users of Red Hat JBoss Enterprise Application Platform 6.3.0 on Red Hat Enterprise Linux 5, 6, and 7 are advised to upgrade to these updated packages. The JBoss server process must be restarted for the update to take effect.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied. Also, back up any customized Red Hat JBoss Enterprise Application Platform 6 configuration files. On update, the configuration files that have been locally modified will not be updated. The updated version of such files will be stored as the rpmnew files. Make sure to locate any such files after the update and merge any changes manually.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/articles/11258

Affected Products

Updated Packages

• httpcore-eap6-4.2.1-12.redhat_2.1.ep6.el5.noarch.rpm
• httpcomponents-core-eap6-4.2.1-12.redhat_2.1.ep6.el7.noarch.rpm
• httpmime-eap6-4.2.1-12.redhat_2.1.ep6.el6.noarch.rpm
• httpclient-eap6-4.2.1-12.redhat_2.1.ep6.el7.noarch.rpm
• httpcomponents-eap6-6-12.redhat_2.1.ep6.el7.src.rpm
• httpcore-eap6-4.2.1-12.redhat_2.1.ep6.el6.noarch.rpm
• httpcomponents-eap6-6-12.redhat_2.1.ep6.el6.src.rpm
• httpcomponents-client-eap6-4.2.1-12.redhat_2.1.ep6.el5.noarch.rpm
• httpcomponents-eap6-6-12.redhat_2.1.ep6.el5.src.rpm
• httpclient-eap6-4.2.1-12.redhat_2.1.ep6.el6.noarch.rpm
• httpmime-eap6-4.2.1-12.redhat_2.1.ep6.el5.noarch.rpm
• httpclient-eap6-4.2.1-12.redhat_2.1.ep6.el5.noarch.rpm
• httpmime-eap6-4.2.1-12.redhat_2.1.ep6.el7.noarch.rpm
• httpcomponents-client-eap6-4.2.1-12.redhat_2.1.ep6.el6.noarch.rpm
• httpcomponents-core-eap6-4.2.1-12.redhat_2.1.ep6.el5.noarch.rpm
• httpcomponents-client-eap6-4.2.1-12.redhat_2.1.ep6.el7.noarch.rpm
• httpcomponents-project-eap6-6-12.redhat_2.1.ep6.el6.noarch.rpm
• httpcomponents-core-eap6-4.2.1-12.redhat_2.1.ep6.el6.noarch.rpm
• httpcomponents-project-eap6-6-12.redhat_2.1.ep6.el5.noarch.rpm
• httpcomponents-project-eap6-6-12.redhat_2.1.ep6.el7.noarch.rpm
• httpcore-eap6-4.2.1-12.redhat_2.1.ep6.el7.noarch.rpm

Fixes

• This content is not included.BZ - 1129074
• This content is not included.BZ - 1129916

CVEs

• CVE-2012-6153
• CVE-2014-3577

References

• http://www.redhat.com/security/updates/classification/#important

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.