CVE-2018-8039: Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*

Quick answers

Is CVE-2018-8039 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2018-8039 being exploited in the wild.

How severe is CVE-2018-8039?

Low severity, with a CVSS score of 3, published 19 October 2018.

Which products and versions are affected?

org.apache.cxf:apache-cxf (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.5; org.apache.cxf:cxf-rt-transports-http (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.5.

Is there a fix for CVE-2018-8039?

Yes. org.apache.cxf:apache-cxf (Maven): upgrade to 3.2.5 or later; org.apache.cxf:cxf-rt-transports-http (Maven): upgrade to 3.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2018-8039?

Check whether you run org.apache.cxf:apache-cxf (Maven) or org.apache.cxf:cxf-rt-transports-http (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• org.apache.cxf:apache-cxf (Maven): upgrade to 3.2.5 or later

  # set org.apache.cxf:apache-cxf to 3.2.5 in your pom.xml or build.gradle

• org.apache.cxf:cxf-rt-transports-http (Maven): upgrade to 3.2.5 or later

  # set org.apache.cxf:cxf-rt-transports-http to 3.2.5 in your pom.xml or build.gradle

Affected products

• org.apache.cxf:apache-cxf (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.5
• org.apache.cxf:cxf-rt-transports-http (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.5

Identifiers

• CVE-2018-8039
• GHSA-jc7r-v6fg-2gpf