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

> Improper exception handling in Apache CXF allows bypassing TLS hostname verification when using the legacy com.sun.net.ssl stack, enabling man-in-the-middle attacks.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jc7r-v6fg-2gpf

## What is CVE-2018-8039?

CVE-2018-8039 is a high-severity vulnerability in Apache Cxf, published on 2 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2018-8039?

8 open source packages ship an affected version, including org.apache.cxf:apache-cxf and org.apache.cxf:cxf-rt-transports-http. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.cxf:apache-cxf` | Maven | All versions | 3.1.16 |
| `org.apache.cxf:apache-cxf` | Maven | All versions | 3.1.16 |
| `org.apache.cxf:apache-cxf` | Maven | From 3.2.0 | 3.2.5 |
| `org.apache.cxf:apache-cxf` | Maven | From 3.2.0 | 3.2.5 |
| `org.apache.cxf:cxf-rt-transports-http` | Maven | All versions | 3.1.16 |
| `org.apache.cxf:cxf-rt-transports-http` | Maven | All versions | 3.1.16 |
| `org.apache.cxf:cxf-rt-transports-http` | Maven | From 3.2.0 | 3.2.5 |
| `org.apache.cxf:cxf-rt-transports-http` | Maven | From 3.2.0 | 3.2.5 |

Products: Apache Cxf, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2018-8039?

Upgrade org.apache.cxf:apache-cxf to a fixed version for your release line: 3.1.16 or 3.2.5.

## Is CVE-2018-8039 being exploited?

There is no known exploitation of CVE-2018-8039 in the wild and no public exploit code.

Public exploit code:

- https://github.com/tafamace/CVE-2018-8039 (github_poc): https://github.com/tafamace/CVE-2018-8039

## Other vulnerabilities in Apache Cxf

- [CVE-2012-2379](https://insights.sbomify.com/CVE-2012-2379/): XML Signature/Encryption Not Validated in Apache CXF (critical 10.0)
- [CVE-2026-66909](https://insights.sbomify.com/CVE-2026-66909/): Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage (critical 9.8)
- [CVE-2026-68079](https://insights.sbomify.com/CVE-2026-68079/): Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay (critical 9.8)
- [CVE-2026-50628](https://insights.sbomify.com/CVE-2026-50628/): Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control (critical 9.8)
- [CVE-2025-48913](https://insights.sbomify.com/CVE-2025-48913/): Apache CXF: Untrusted JMS configuration can lead to RCE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8039 and fix it if it is affected.

What it is: CVE-2018-8039 is a high-severity vulnerability in Apache Cxf, published on 2 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8039 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.cxf:apache-cxf (Maven): affected all versions; fixed in 3.1.16
- org.apache.cxf:apache-cxf (Maven): affected all versions; fixed in 3.1.16
- org.apache.cxf:apache-cxf (Maven): affected from 3.2.0; fixed in 3.2.5
- org.apache.cxf:apache-cxf (Maven): affected from 3.2.0; fixed in 3.2.5
- org.apache.cxf:cxf-rt-transports-http (Maven): affected all versions; fixed in 3.1.16
- org.apache.cxf:cxf-rt-transports-http (Maven): affected all versions; fixed in 3.1.16
- org.apache.cxf:cxf-rt-transports-http (Maven): affected from 3.2.0; fixed in 3.2.5
- org.apache.cxf:cxf-rt-transports-http (Maven): affected from 3.2.0; fixed in 3.2.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8039/ (Markdown: https://insights.sbomify.com/CVE-2018-8039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8039
- OSV: https://osv.dev/vulnerability/CVE-2018-8039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8039/
Summaries are generated and may contain mistakes; the official description above is the record.