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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
EUVD-2018-0630 | Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.* |
![]() |
GHSA-jc7r-v6fg-2gpf | Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.* |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 23 Aug 2024 05:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
CPEs | cpe:/a:redhat:jboss_enterprise_application_platform:7.1::el7 |

Status: PUBLISHED
Assigner: apache
Published:
Updated: 2024-09-17T04:04:46.184Z
Reserved: 2018-03-09T00:00:00
Link: CVE-2018-8039

No data.

Status : Modified
Published: 2018-07-02T13:29:00.413
Modified: 2024-11-21T04:13:09.517
Link: CVE-2018-8039


No data.