LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8039: It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty("j...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE affects Apache CXF clients that are configured to use the legacy com.sun.net.ssl protocol stack. In that uncommon configuration, CXF may fail to enforce TLS hostname verification correctly, exposing client connections to man-in-the-middle interception. Business urgency depends on whether affected CXF versions and this legacy Java setting are present. Exposure is likely limited to Java applications using vulnerable Apache CXF versions and explicitly enabling the legacy com.sun.net.ssl protocol handler. Internet-facing servers are not the primary concern; outbound CXF client connections carrying sensitive data are the main risk. Prioritize assessment where Java services use Apache CXF for sensitive outbound connections. This is not broadly exploitable by default, but affected configurations undermine TLS trust and can expose credentials or data if traffic is intercepted. Mitigation focus: Upgrade Apache CXF to 3.1.16, 3.2.5, or later supported versions.; Review Red Hat advisories if CXF is supplied through Red Hat packages.; Remove legacy com.sun.net.ssl protocol handler usage where feasible..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-8039 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
22Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache CXFprior to 3.1.16, 3.2.x prior to 3.2.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.