CVE-2018-8039 Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*
Improper exception handling in Apache CXF allows bypassing TLS hostname verification when using the legacy com.sun.net.ssl stack, enabling man-in-the-middle attacks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2018-8039?
CVE-2018-8039 is a high-severity vulnerability in Apache Cxf, published on 2 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");'. When this system property is set, CXF uses some reflection to try to make the HostnameVerifier work with the old com.sun.net.ssl.HostnameVerifier interface. However, the default HostnameVerifier implementation in CXF does not implement the method in this interface, and an exception is thrown. However, in Apache CXF prior to 3.2.5 and 3.1.16 the exception is caught in the reflection code and not properly propagated. What this means is that if you are using the com.sun.net.ssl stack with CXF, an error with TLS hostname verification will not be thrown, leaving a CXF client subject to man-in-the-middle attacks.
Weakness: CWE-755
Which versions are affected by CVE-2018-8039?
8 open source packages ship an affected version, including org.apache.cxf:apache-cxf and org.apache.cxf:cxf-rt-transports-http. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.cxf:apache-cxf Maven | All versions | 3.1.16 |
org.apache.cxf:apache-cxf Maven | All versions | 3.1.16 |
org.apache.cxf:apache-cxf Maven | From 3.2.0 | 3.2.5 |
org.apache.cxf:apache-cxf Maven | From 3.2.0 | 3.2.5 |
org.apache.cxf:cxf-rt-transports-http Maven | All versions | 3.1.16 |
org.apache.cxf:cxf-rt-transports-http Maven | All versions | 3.1.16 |
2 more packages
org.apache.cxf:cxf-rt-transports-http Maven | From 3.2.0 | 3.2.5 |
org.apache.cxf:cxf-rt-transports-http Maven | From 3.2.0 | 3.2.5 |
Products include Apache Cxf, Redhat Jboss Enterprise Application Platform.
How do I fix CVE-2018-8039?
Upgrade org.apache.cxf:apache-cxf to a fixed version for your release line: 3.1.16 or 3.2.5.
Is CVE-2018-8039 being exploited?
There is no known exploitation of CVE-2018-8039 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Apache Cxf
- CVE-2012-2379 XML Signature/Encryption Not Validated in Apache CXF
- CVE-2026-66909 Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage
- CVE-2026-68079 Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay
- CVE-2026-50628 Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control
- CVE-2025-48913 Apache CXF: Untrusted JMS configuration can lead to RCE
Sources
Also known as GHSA-jc7r-v6fg-2gpf.