CVE Database
/

CVE-2018-8039

Back to search

CVE-2018-8039

Published: Jul 2, 2018

Modified: Sep 17, 2024

PUBLISHED

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.

VendorProductVersions

Apache Software Foundation

Apache CXF

affected
prior to 3.1.16
affected
3.2.x prior to 3.2.5

References

RHSA-2018:2428
vendor-advisory
x_refsource_REDHAT
RHSA-2018:3817
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2643
vendor-advisory
x_refsource_REDHAT
106357
vdb-entry
x_refsource_BID
RHSA-2018:2279
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2424
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2276
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2423
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2425
vendor-advisory
x_refsource_REDHAT
RHSA-2018:2277
vendor-advisory
x_refsource_REDHAT
1041199
vdb-entry
x_refsource_SECTRACK
RHSA-2018:3768
vendor-advisory
x_refsource_REDHAT

Security Training

Train your team to recognize and prevent security threats with our comprehensive security awareness program.

Start Training

Vulnerability Scanning

Discover vulnerabilities in your applications and infrastructure before attackers do.

Scan Now