Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2018-8039: 8.51% estimated exploitation activity in the next 30 days; percentile 95.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

19 Oct 2018, 16:40 UTC

Last modified by the source

29 May 2025, 17:42 UTC

Source last checked

26 Oct 2026, 16:36 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jc7r-v6fg-2gpf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-8039

Advisory: Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*
IDs: CVE-2018-8039, GHSA-jc7r-v6fg-2gpf
Record: https://patchnext.com/advisories/cve-2018-8039 (revision 1, source checked 26 Oct 2026, 16:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.cxf:cxf-rt-transports-http 3.2.5, 3.1.16; org.apache.cxf:apache-cxf 3.2.5, 3.1.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.cxf:cxf-rt-transports-http: affected >= 3.2.0, < 3.2.5; < 3.1.16; fixed in 3.1.16, 3.2.5
- Maven org.apache.cxf:apache-cxf: affected >= 3.2.0, < 3.2.5; < 3.1.16; fixed in 3.1.16, 3.2.5

## Suggested inspection (read-only)
- Maven org.apache.cxf:cxf-rt-transports-http: check the installed version with your package manager.
- Maven org.apache.cxf:apache-cxf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.cxf:cxf-rt-transports-http, org.apache.cxf:apache-cxf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jc7r-v6fg-2gpf (GitHub-reviewed advisory GHSA-jc7r-v6fg-2gpf lists affected ranges: Maven org.apache.cxf:apache-cxf >=3.2.0 =0 =3.2.0 =0 <3.1.16)

Commands are suggestions: review each one before running it.