CVE & CISA-KEV Catalog

CVE-2018-8039

HIGHEPSS 95th pctl
8.1
CVSS v3
NVD

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.

How to fix

Remediation Available
cxfNVD
Affected:>= 3.2.0, < 3.2.5Fixed in:3.2.5CVE-2018-8039derived from NVD

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

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

Exploit Intelligence

10.35%probability of exploitation in 30 days
95thpercentile

Very high risk: more likely to be exploited than 95% of all known CVEs.

References

Related Vulnerabilities

Other CWE-755 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2017-5638Critical9.8100%KEV + RansomFix
CVE-2020-7247Critical9.899%KEVFix
CVE-2023-36933High7.572%-Fix
CVE-2018-0934High7.567%-Fix
CVE-2019-14287High8.864%-Fix
CVE-2019-12815Critical9.858%-Fix

Common questions

How do I fix CVE-2018-8039?

Upgrade cxf to 3.2.5 or later.

Is CVE-2018-8039 being actively exploited?

Not that we know of. CVE-2018-8039 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 10.3% is the estimated probability that it will be exploited in the next 30 days. That is higher than 95% of all scored CVEs.

How severe is CVE-2018-8039?

CVE-2018-8039 has a CVSS v3 base score of 8.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2018-8039 affect?

Published advisories record a fix for cxf (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2018-8039
CVE-2018-8039 severity badge

Markdown

[![CVE-2018-8039](https://tridentstack.com/cve/badge/CVE-2018-8039.svg)](https://tridentstack.com/cve/CVE-2018-8039)

HTML

<a href="https://tridentstack.com/cve/CVE-2018-8039"><img src="https://tridentstack.com/cve/badge/CVE-2018-8039.svg" alt="CVE-2018-8039"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.