SOC status:Duty analyst on shift

UK Cyber Defence
VulnerabilityModified

CVE-2018-8039

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");'.

HIGH 8.1EPSS 8.51%

Does this matter?

High impact if exploited, but EPSS currently rates exploitation as unlikely (8.51%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.

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.

CVSS 3.0
8.1 HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
8.51% probability · 95th percentile
Public exploits
None in Exploit-DB
CISA KEV
Not listed
Weakness
CWE-755
Affected
apache/cxf · redhat/jboss enterprise application platform
Source
security@apache.org
EPSS trend
0%5%10%27 October 2026: 8.51%27 October 202627 October 2026

EPSS 8.5% since 27 October 2026; no change recorded yet. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”. Points are recorded when the score first appears and whenever it moves by a percentage point or more.

References

Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.