First published: Mon Mar 25 2013(Updated: )
The Jakarta Commons HttpClient component can be used to build HTTP-aware<br>client applications (such as web browsers and web service clients).<br>The Jakarta Commons HttpClient component did not verify that the server<br>hostname matched the domain name in the subject's Common Name (CN) or<br>subjectAltName field in X.509 certificates. This could allow a<br>man-in-the-middle attacker to spoof an SSL server if they had a certificate<br>that was valid for any domain name. (CVE-2012-5783)<br>Warning: Before applying this update, back up your existing JBoss<br>Enterprise Application Platform installation (including all applications<br>and configuration files).<br>All users of JBoss Enterprise Application Platform 5.2.0 as provided from<br>the Red Hat Customer Portal are advised to apply this update.
Affected Software | Affected Version | How to fix |
---|---|---|
JBoss Enterprise Application Platform | ||
Apache Commons HttpClient |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2013:0679 is classified as moderate.
To fix RHSA-2013:0679, you should update the Jakarta Commons HttpClient component to the latest version that addresses the vulnerability.
RHSA-2013:0679 addresses a vulnerability in the Jakarta Commons HttpClient that fails to verify the server hostname against the domain name in the certificate.
Individuals and organizations using affected versions of the Jakarta Commons HttpClient component may be vulnerable to this issue.
The potential risks of RHSA-2013:0679 include exposure to man-in-the-middle attacks due to improper SSL/TLS hostname verification.