Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*
Apache Software Foundation Apache CXF
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf-rt-transports-http Maven |
|
|
| org.apache.cxf:apache-cxf Maven |
|
Apache Software Foundation Apache CXF
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf-rt-transports-http Maven |
|
|
| org.apache.cxf:apache-cxf Maven |
|
|
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.
From the CVE record · apache
Apache CXF clients using the com.sun.net.ssl stack can fail to report TLS hostname verification errors because an exception is caught and not properly propagated. When the specified java.protocol.handler.pkgs system property selects that stack, this can leave the client subject to a network man-in-the-middle attack.
Check applications using Apache CXF or the Maven packages org.apache.cxf:cxf-rt-transports-http and org.apache.cxf:apache-cxf on versions before 3.1.16 or from 3.2.0 to before 3.2.5.