Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.apache.cxf/apache-cxf
  4. ›
  5. CVE-2018-8039

CVE-2018-8039: Improper Handling of Exceptional Conditions

October 19, 2018 (updated December 3, 2021)

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.

References

  • github.com/advisories/GHSA-jc7r-v6fg-2gpf

Code Behaviors & Features

Detect and mitigate CVE-2018-8039 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 3.2.0 before 3.2.5, all versions before 3.1.16

Fixed versions

  • 3.1.16

Solution

Upgrade to version 3.1.16 or above.

Impact 8.1 HIGH

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

Learn more about CVSS

Weakness

  • CWE-755: Improper Handling of Exceptional Conditions

Source file

maven/org.apache.cxf/apache-cxf/CVE-2018-8039.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:44 +0000.