CVE-2018-8039 – org.apache.cxf:apache-cxf

Package

Manager: maven
Name: org.apache.cxf:apache-cxf
Vulnerable Version: >=3.2.0 <3.2.5 || >=0 <3.1.16

Severity

Level: High

CVSS v3.1: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

EPSS: 0.0191 pctl0.82579

Details

Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.* 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.

Metadata

Created: 2018-10-19T16:40:01Z
Modified: 2025-05-29T17:42:39Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/10/GHSA-jc7r-v6fg-2gpf/GHSA-jc7r-v6fg-2gpf.json
CWE IDs: ["CWE-755"]
Alternative ID: GHSA-jc7r-v6fg-2gpf
Finding: F096
Auto approve: 1