cve.bz

CVE-2018-8039

8.1 highEPSS 8.5%

High (8.1). EPSS 8.5% chance of exploitation in the next 30 days. Fixed in org.apache.cxf:cxf-rt-transports-http 3.1.16, 3.2.5.

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.

Severity

CVSS 3.0

8.1 high
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
8.5% chance of exploitation in the next 30 days; higher than 95% of CVEs (scores of 2026-10-31)
CWE
CWE-755
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jc7r-v6fg-2gpfMavenorg.apache.cxf:cxf-rt-transports-http>=3.2.0 <3.2.53.2.5
GHSA-jc7r-v6fg-2gpfMavenorg.apache.cxf:cxf-rt-transports-http<3.1.163.1.16
GHSA-jc7r-v6fg-2gpfMavenorg.apache.cxf:apache-cxf>=3.2.0 <3.2.53.2.5
GHSA-jc7r-v6fg-2gpfMavenorg.apache.cxf:apache-cxf<3.1.163.1.16

References

Check your stackJSON