Skip to content
fr Sign in
Not rated

CVE-2018-8039 It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via…

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.

Affected products and versions

Product Affected versions Fixed in
Apache CXF Versions not published

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache CXF

The 56 CVEs of Apache CXF →
CVE-2026-108039 By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML… Not rated CVE-2026-107938 In Apache CXF, the Netty-based HTTP client transport (cxf-rt-transports-http-netty-client) did not verify that the… Not rated CVE-2026-107937 In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured… Not rated CVE-2026-100227 Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security module Not rated
Track this CVE