Vulnerabilities · 2018 · Apache
CVE-2018-8039
Apache Cxf vulnerability
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.
Affected products
Cxf, Jboss Enterprise Application Platform. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Apache Cxf runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- cxf.apache.org/security-advisories.data/CVE-2018-8039.txt.asc?version=1&modificationDate=1 · Vendor Advisory
- github.com/apache/cxf/commit/fae6fabf9bd7647f5e9cb68897a7d72b545b741b · Patch
- www.securitytracker.com/id/1041199 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2276 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2277 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2279 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2423 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2424 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2018-8039
- cve.org/CVERecord?id=CVE-2018-8039
More vulnerabilities in Apache products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.