# CVE-2017-12624: Improper Input Validation in Apache CXF

> Attackers can cause denial of service in Apache CXF web services by sending crafted message attachment headers exceeding default size limits.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7vgj-8mw4-hg8r

## What is CVE-2017-12624?

CVE-2017-12624 is a medium-severity denial of service vulnerability in Apache Cxf, published on 14 Nov 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Apache CXF supports sending and receiving attachments via either the JAX-WS or JAX-RS specifications. It is possible to craft a message attachment header that could lead to a Denial of Service (DoS) attack on a CXF web service provider. Both JAX-WS and JAX-RS services are vulnerable to this attack. From Apache CXF 3.2.1 and 3.1.14, message attachment headers that are greater than 300 characters will be rejected by default. This value is configurable via the property "attachment-max-header-size".

## Which versions are affected by CVE-2017-12624?

6 open source packages ship an affected version, including org.apache.cxf:cxf-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.cxf:cxf-core` | Maven | All versions | 3.0.16 |
| `org.apache.cxf:cxf-core` | Maven | All versions | 3.0.16 |
| `org.apache.cxf:cxf-core` | Maven | From 3.1.0 | 3.1.14 |
| `org.apache.cxf:cxf-core` | Maven | From 3.1.0 | 3.1.14 |
| `org.apache.cxf:cxf-core` | Maven | From 3.2.0 | 3.2.1 |
| `org.apache.cxf:cxf-core` | Maven | From 3.2.0 | 3.2.1 |

Products: Apache Cxf.

## How do I fix CVE-2017-12624?

Upgrade org.apache.cxf:cxf-core to a fixed version for your release line: 3.0.16, 3.1.14 or 3.2.1.

## Is CVE-2017-12624 being exploited?

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

Public exploit code:

- https://github.com/tafamace/CVE-2017-12624 (github_poc): https://github.com/tafamace/CVE-2017-12624

## 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-2017-12624 and fix it if it is affected.

What it is: CVE-2017-12624 is a medium-severity denial of service vulnerability in Apache Cxf, published on 14 Nov 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12624 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.0.16
- org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.0.16
- org.apache.cxf:cxf-core (Maven): affected from 3.1.0; fixed in 3.1.14
- org.apache.cxf:cxf-core (Maven): affected from 3.1.0; fixed in 3.1.14
- org.apache.cxf:cxf-core (Maven): affected from 3.2.0; fixed in 3.2.1
- org.apache.cxf:cxf-core (Maven): affected from 3.2.0; fixed in 3.2.1

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-2017-12624/ (Markdown: https://insights.sbomify.com/CVE-2017-12624/index.md)
```

## Sources

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

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