CVE-2014-3577: Medium severity Apache HttpClient vulnerability

Published Aug 12, 2014
·
Updated

It was found that the fix for CVE-2012-6153 was incomplete: the code added to check that the server hostname 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.

Other sources

It was found that the fix for CVE-2012-6153 was incomplete. The code added to check that the server hostname matches the domain name in the subject's CN field was flawed. This can be exploited by a Man-in-the-middle (MITM) attack where the attacker can spoof a valid certificate using a specially crafted subject.

— Red Hat

org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a "CN=" string in a field in the distinguished name (DN) of a certificate, as demonstrated by the "foo,CN=

— IBM

Affected Software

59 affected componentsFixes available
redhat/jakarta-commons-httpclient<1:3.1-4_patch_02.ep5.el5
1:3.1-4_patch_02.ep5.el5
redhat/jboss-seam2<0:2.2.6.EAP5-22_patch_01.ep5.el5
0:2.2.6.EAP5-22_patch_01.ep5.el5
redhat/apache-cxf<0:2.2.12-14.patch_09.ep5.el5
0:2.2.12-14.patch_09.ep5.el5
redhat/jakarta-commons-httpclient<1:3.1-4_patch_02.el6_5
1:3.1-4_patch_02.el6_5
redhat/jboss-seam2<0:2.2.6.EAP5-22_patch_01.el6
0:2.2.6.EAP5-22_patch_01.el6
redhat/apache-cxf<0:2.2.12-14.patch_09.el6
0:2.2.12-14.patch_09.el6
redhat/jakarta-commons-httpclient<1:3.0-7jpp.4.el5_10
1:3.0-7jpp.4.el5_10
redhat/jakarta-commons-httpclient<1:3.1-0.9.el6_5
1:3.1-0.9.el6_5
redhat/httpcomponents-client<0:4.2.5-5.el7_0
0:4.2.5-5.el7_0
redhat/jakarta-commons-httpclient<1:3.1-16.el7_0
1:3.1-16.el7_0
redhat/jakarta-commons-httpclient<1:3.1-4_patch_02.ep5.el4
1:3.1-4_patch_02.ep5.el4
redhat/jboss-seam2<0:2.2.6.EAP5-22_patch_01.ep5.el4
0:2.2.6.EAP5-22_patch_01.ep5.el4
redhat/apache-cxf<0:2.2.12-14.patch_09.ep5.el4
0:2.2.12-14.patch_09.ep5.el4
redhat/httpcomponents-eap6<0:6-12.redhat_2.1.ep6.el5
0:6-12.redhat_2.1.ep6.el5
redhat/apache-cxf<0:2.7.12-1.SP1_redhat_5.1.ep6.el5
0:2.7.12-1.SP1_redhat_5.1.ep6.el5
redhat/wss4j<0:1.6.16-2.redhat_3.1.ep6.el5
0:1.6.16-2.redhat_3.1.ep6.el5
redhat/httpcomponents-eap6<0:6-12.redhat_2.1.ep6.el6
0:6-12.redhat_2.1.ep6.el6
redhat/apache-cxf<0:2.7.12-1.SP1_redhat_5.1.ep6.el6
0:2.7.12-1.SP1_redhat_5.1.ep6.el6
redhat/wss4j<0:1.6.16-2.redhat_3.1.ep6.el6
0:1.6.16-2.redhat_3.1.ep6.el6
redhat/httpcomponents-eap6<0:6-12.redhat_2.1.ep6.el7
0:6-12.redhat_2.1.ep6.el7
redhat/apache-cxf<0:2.7.12-1.SP1_redhat_5.1.ep6.el7
0:2.7.12-1.SP1_redhat_5.1.ep6.el7
redhat/wss4j<0:1.6.16-2.redhat_3.1.ep6.el7
0:1.6.16-2.redhat_3.1.ep6.el7
redhat/jenkins<0:2.319.2.1643288987-1.el8
0:2.319.2.1643288987-1.el8
redhat/activemq<0:5.9.0-6.redhat.611463.el6
0:5.9.0-6.redhat.611463.el6
redhat/jenkins<0:1.651.2-1.el6
0:1.651.2-1.el6
redhat/libcgroup<0:0.40.rc1-18.el6_8
0:0.40.rc1-18.el6_8
redhat/openshift-origin-broker<0:1.16.3.2-1.el6
0:1.16.3.2-1.el6
redhat/openshift-origin-broker-util<0:1.37.6.2-1.el6
0:1.37.6.2-1.el6
redhat/openshift-origin-cartridge-cron<0:1.25.4.2-1.el6
0:1.25.4.2-1.el6
redhat/openshift-origin-cartridge-diy<0:1.26.2.2-1.el6
0:1.26.2.2-1.el6
redhat/openshift-origin-cartridge-haproxy<0:1.31.6.2-1.el6
0:1.31.6.2-1.el6
redhat/openshift-origin-cartridge-jbosseap<0:2.27.4.2-1.el6
0:2.27.4.2-1.el6
redhat/openshift-origin-cartridge-jbossews<0:1.35.5.2-1.el6
0:1.35.5.2-1.el6
redhat/openshift-origin-cartridge-jenkins<0:1.29.2.2-1.el6
0:1.29.2.2-1.el6
redhat/openshift-origin-cartridge-jenkins-client<0:1.26.1.1-1.el6
0:1.26.1.1-1.el6
redhat/openshift-origin-cartridge-mongodb<0:1.26.2.2-1.el6
0:1.26.2.2-1.el6
redhat/openshift-origin-cartridge-mysql<0:1.31.3.3-1.el6
0:1.31.3.3-1.el6
redhat/openshift-origin-cartridge-nodejs<0:1.33.1.2-1.el6
0:1.33.1.2-1.el6
redhat/openshift-origin-cartridge-perl<0:1.30.2.2-1.el6
0:1.30.2.2-1.el6
redhat/openshift-origin-cartridge-php<0:1.35.4.2-1.el6
0:1.35.4.2-1.el6
redhat/openshift-origin-cartridge-python<0:1.34.3.2-1.el6
0:1.34.3.2-1.el6
redhat/openshift-origin-cartridge-ruby<0:1.32.2.2-1.el6
0:1.32.2.2-1.el6
redhat/openshift-origin-msg-node-mcollective<0:1.30.2.2-1.el6
0:1.30.2.2-1.el6
redhat/openshift-origin-node-proxy<0:1.26.3.1-1.el6
0:1.26.3.1-1.el6
redhat/openshift-origin-node-util<0:1.38.7.1-1.el6
0:1.38.7.1-1.el6
redhat/rhc<0:1.38.7.1-1.el6
0:1.38.7.1-1.el6
redhat/rubygem-openshift-origin-admin-console<0:1.28.2.1-1.el6
0:1.28.2.1-1.el6
redhat/rubygem-openshift-origin-controller<0:1.38.6.4-1.el6
0:1.38.6.4-1.el6
redhat/rubygem-openshift-origin-frontend-haproxy-sni-proxy<0:0.5.2.1-1.el6
0:0.5.2.1-1.el6
redhat/rubygem-openshift-origin-msg-broker-mcollective<0:1.36.2.4-1.el6
0:1.36.2.4-1.el6
redhat/rubygem-openshift-origin-node<0:1.38.6.4-1.el6
0:1.38.6.4-1.el6
redhat/rubygem-openshift-origin-routing-daemon<0:0.26.6.1-1.el6
0:0.26.6.1-1.el6
redhat/thermostat1-httpcomponents-client<0:4.2.5-3.4.el6.1
0:4.2.5-3.4.el6.1
maven/org.apache.httpcomponents:httpclient<4.3.5
4.3.5
Apache HttpClient>=4.0<=4.3.4
Apache HttpAsyncClient>=4.0<=4.0.1
redhat/httpcomponents-client<4.3.5
4.3.5
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.7.2.1 - 9.7.2.11
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.6.1.1 - 9.6.1.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.1-4_patch_02.ep5.el5
  2. Upgrade

    Upgrade redhat/jboss-seam2 to a version that resolves this vulnerability.

    Fixed in 0:2.2.6.EAP5-22_patch_01.ep5.el5
  3. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.2.12-14.patch_09.ep5.el5
  4. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.1-4_patch_02.el6_5
  5. Upgrade

    Upgrade redhat/jboss-seam2 to a version that resolves this vulnerability.

    Fixed in 0:2.2.6.EAP5-22_patch_01.el6
  6. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.2.12-14.patch_09.el6
  7. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.0-7jpp.4.el5_10
  8. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.1-0.9.el6_5
  9. Upgrade

    Upgrade redhat/httpcomponents-client to a version that resolves this vulnerability.

    Fixed in 0:4.2.5-5.el7_0
  10. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.1-16.el7_0
  11. Upgrade

    Upgrade redhat/jakarta-commons-httpclient to a version that resolves this vulnerability.

    Fixed in 1:3.1-4_patch_02.ep5.el4
  12. Upgrade

    Upgrade redhat/jboss-seam2 to a version that resolves this vulnerability.

    Fixed in 0:2.2.6.EAP5-22_patch_01.ep5.el4
  13. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.2.12-14.patch_09.ep5.el4
  14. Upgrade

    Upgrade redhat/httpcomponents-eap6 to a version that resolves this vulnerability.

    Fixed in 0:6-12.redhat_2.1.ep6.el5
  15. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.7.12-1.SP1_redhat_5.1.ep6.el5
  16. Upgrade

    Upgrade redhat/wss4j to a version that resolves this vulnerability.

    Fixed in 0:1.6.16-2.redhat_3.1.ep6.el5
  17. Upgrade

    Upgrade redhat/httpcomponents-eap6 to a version that resolves this vulnerability.

    Fixed in 0:6-12.redhat_2.1.ep6.el6
  18. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.7.12-1.SP1_redhat_5.1.ep6.el6
  19. Upgrade

    Upgrade redhat/wss4j to a version that resolves this vulnerability.

    Fixed in 0:1.6.16-2.redhat_3.1.ep6.el6
  20. Upgrade

    Upgrade redhat/httpcomponents-eap6 to a version that resolves this vulnerability.

    Fixed in 0:6-12.redhat_2.1.ep6.el7
  21. Upgrade

    Upgrade redhat/apache-cxf to a version that resolves this vulnerability.

    Fixed in 0:2.7.12-1.SP1_redhat_5.1.ep6.el7
  22. Upgrade

    Upgrade redhat/wss4j to a version that resolves this vulnerability.

    Fixed in 0:1.6.16-2.redhat_3.1.ep6.el7
  23. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 0:2.319.2.1643288987-1.el8
  24. Upgrade

    Upgrade redhat/activemq to a version that resolves this vulnerability.

    Fixed in 0:5.9.0-6.redhat.611463.el6
  25. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 0:1.651.2-1.el6
  26. Upgrade

    Upgrade redhat/libcgroup to a version that resolves this vulnerability.

    Fixed in 0:0.40.rc1-18.el6_8
  27. Upgrade

    Upgrade redhat/openshift-origin-broker to a version that resolves this vulnerability.

    Fixed in 0:1.16.3.2-1.el6
  28. Upgrade

    Upgrade redhat/openshift-origin-broker-util to a version that resolves this vulnerability.

    Fixed in 0:1.37.6.2-1.el6
  29. Upgrade

    Upgrade redhat/openshift-origin-cartridge-cron to a version that resolves this vulnerability.

    Fixed in 0:1.25.4.2-1.el6
  30. Upgrade

    Upgrade redhat/openshift-origin-cartridge-diy to a version that resolves this vulnerability.

    Fixed in 0:1.26.2.2-1.el6
  31. Upgrade

    Upgrade redhat/openshift-origin-cartridge-haproxy to a version that resolves this vulnerability.

    Fixed in 0:1.31.6.2-1.el6
  32. Upgrade

    Upgrade redhat/openshift-origin-cartridge-jbosseap to a version that resolves this vulnerability.

    Fixed in 0:2.27.4.2-1.el6
  33. Upgrade

    Upgrade redhat/openshift-origin-cartridge-jbossews to a version that resolves this vulnerability.

    Fixed in 0:1.35.5.2-1.el6
  34. Upgrade

    Upgrade redhat/openshift-origin-cartridge-jenkins to a version that resolves this vulnerability.

    Fixed in 0:1.29.2.2-1.el6
  35. Upgrade

    Upgrade redhat/openshift-origin-cartridge-jenkins-client to a version that resolves this vulnerability.

    Fixed in 0:1.26.1.1-1.el6
  36. Upgrade

    Upgrade redhat/openshift-origin-cartridge-mongodb to a version that resolves this vulnerability.

    Fixed in 0:1.26.2.2-1.el6
  37. Upgrade

    Upgrade redhat/openshift-origin-cartridge-mysql to a version that resolves this vulnerability.

    Fixed in 0:1.31.3.3-1.el6
  38. Upgrade

    Upgrade redhat/openshift-origin-cartridge-nodejs to a version that resolves this vulnerability.

    Fixed in 0:1.33.1.2-1.el6
  39. Upgrade

    Upgrade redhat/openshift-origin-cartridge-perl to a version that resolves this vulnerability.

    Fixed in 0:1.30.2.2-1.el6
  40. Upgrade

    Upgrade redhat/openshift-origin-cartridge-php to a version that resolves this vulnerability.

    Fixed in 0:1.35.4.2-1.el6
  41. Upgrade

    Upgrade redhat/openshift-origin-cartridge-python to a version that resolves this vulnerability.

    Fixed in 0:1.34.3.2-1.el6
  42. Upgrade

    Upgrade redhat/openshift-origin-cartridge-ruby to a version that resolves this vulnerability.

    Fixed in 0:1.32.2.2-1.el6
  43. Upgrade

    Upgrade redhat/openshift-origin-msg-node-mcollective to a version that resolves this vulnerability.

    Fixed in 0:1.30.2.2-1.el6
  44. Upgrade

    Upgrade redhat/openshift-origin-node-proxy to a version that resolves this vulnerability.

    Fixed in 0:1.26.3.1-1.el6
  45. Upgrade

    Upgrade redhat/openshift-origin-node-util to a version that resolves this vulnerability.

    Fixed in 0:1.38.7.1-1.el6
  46. Upgrade

    Upgrade redhat/rhc to a version that resolves this vulnerability.

    Fixed in 0:1.38.7.1-1.el6
  47. Upgrade

    Upgrade redhat/rubygem-openshift-origin-admin-console to a version that resolves this vulnerability.

    Fixed in 0:1.28.2.1-1.el6
  48. Upgrade

    Upgrade redhat/rubygem-openshift-origin-controller to a version that resolves this vulnerability.

    Fixed in 0:1.38.6.4-1.el6
  49. Upgrade

    Upgrade redhat/rubygem-openshift-origin-frontend-haproxy-sni-proxy to a version that resolves this vulnerability.

    Fixed in 0:0.5.2.1-1.el6
  50. Upgrade

    Upgrade redhat/rubygem-openshift-origin-msg-broker-mcollective to a version that resolves this vulnerability.

    Fixed in 0:1.36.2.4-1.el6
  51. Upgrade

    Upgrade redhat/rubygem-openshift-origin-node to a version that resolves this vulnerability.

    Fixed in 0:1.38.6.4-1.el6
  52. Upgrade

    Upgrade redhat/rubygem-openshift-origin-routing-daemon to a version that resolves this vulnerability.

    Fixed in 0:0.26.6.1-1.el6
  53. Upgrade

    Upgrade redhat/thermostat1-httpcomponents-client to a version that resolves this vulnerability.

    Fixed in 0:4.2.5-3.4.el6.1
  54. Upgrade

    Upgrade maven/org.apache.httpcomponents:httpclient to a version that resolves this vulnerability.

    Fixed in 4.3.5
  55. Upgrade

    Upgrade redhat/httpcomponents-client to a version that resolves this vulnerability.

    Fixed in 4.3.5
  56. Upgrade

    Upgrade org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient/HttpAsyncClient to a version that resolves this vulnerability.

    Fixed in 4.3.5
  57. Upgrade

    Upgrade org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient/HttpAsyncClient to a version that resolves this vulnerability.

    Fixed in 4.0.2
  58. Compensating control

    Mitigate MITM risk by restricting network access to only trusted endpoints and preventing attackers from intercepting/impersonating SSL servers (e.g., enforce network segmentation/ACLs so clients cannot reach untrusted hosts that could present spoofed certificates).

Event History

Aug 12, 2014
Data Sourced
via Red Hat·08:21 AM
DescriptionSeverityAffected Software
Aug 18, 2014
CVE Published
12:00 AM
Aug 21, 2014
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Oct 17, 2018
Advisory Published
via GitHub·12:05 AM
Jul 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2014-3577?

The severity of CVE-2014-3577 is classified as medium due to the potential for man-in-the-middle attacks.

2

How do I fix CVE-2014-3577?

To fix CVE-2014-3577, you should upgrade to Apache HttpClient version 4.3.5 or higher.

3

Which versions are affected by CVE-2014-3577?

Versions of Apache HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 are affected by CVE-2014-3577.

4

What is the impact of CVE-2014-3577?

CVE-2014-3577 allows attackers to perform man-in-the-middle attacks due to improper hostname verification.

5

Is CVE-2014-3577 exploitable remotely?

Yes, CVE-2014-3577 is exploitable remotely as it involves network communications that can be intercepted.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203