CVE-2013-4366: Hostname verification disabled by default in Apache HttpClient 4.3
Summary
CVE-2013-4366: Hostname verification in Apache HttpClient 4.3 was disabled by default. Affects org.apache.httpcomponents:httpclient versions >= 4.3, < 4.3.1. Fixed in 4.3.1. How to fix ↓
Also tracked for
- httpcomponents-client · Debian:11
The same CVE-2013-4366 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache HttpClient is a widely used Java library for making HTTP requests. It provides a comprehensive set of features for interacting with HTTP servers. The vulnerability in Apache HttpClient 4.3.x before 4.3.1 relates to the hostname verification functionality. By default, the hostname verification was disabled, allowing attackers to exploit this weakness.
Vulnerability Detail
The vulnerability in Apache HttpClient 4.3.x before 4.3.1 arises from the lack of proper validation of the X509HostnameVerifier. This oversight enables attackers to carry out various attacks involving hostname verification. The impact of these attacks can vary and is unspecified. However, it can potentially lead to severe consequences, including unauthorized access, data leakage, and man-in-the-middle attacks.
How To Fix
Latest published version: 4.5.14 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
4.3.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, upgrading to the fixed version is the recommended solution.
Conclusion
The vulnerability in Apache HttpClient 4.3.x before 4.3.1 allows attackers to exploit the disabled hostname verification functionality. To mitigate this risk, it is crucial to upgrade to Apache HttpClient version 4.3.1 or later. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for org.apache.httpcomponents:httpclient →
FAQ
Apache HttpClient is a Java library for making HTTP requests. It provides a wide range of features and functionality for interacting with HTTP servers.
Hostname verification is the process of validating the hostname of a server during an SSL/TLS handshake. It ensures that the server's identity matches the expected hostname.
The impact of this vulnerability can vary and is unspecified. However, it can potentially lead to unauthorized access, data leakage, and man-in-the-middle attacks.
To fix this vulnerability, you should upgrade to Apache HttpClient version 4.3.1 or later.
There is no specific workaround mentioned for this vulnerability. Upgrading to the fixed version is the recommended solution.
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.httpcomponents:httpclient.
