CVE-2017-12624

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".

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2017-12624 has a CVSS score of 5.5 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.1, 3.1.14, 3.0.16); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2017-12624? CVE-2017-12624 is a medium-severity improper input validation vulnerability in org.apache.cxf:cxf-core (maven), affecting versions = 3.2.0. It is fixed in 3.2.1, 3.1.14, 3.0.16. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2017-12624? CVE-2017-12624 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.cxf:cxf-core are affected by CVE-2017-12624? org.apache.cxf:cxf-core (maven) versions = 3.2.0 is affected.
4. Is there a fix for CVE-2017-12624? Yes. CVE-2017-12624 is fixed in 3.2.1, 3.1.14, 3.0.16. Upgrade to this version or later.
5. Is CVE-2017-12624 exploitable, and should I be worried? Whether CVE-2017-12624 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-12624 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-12624?
   • Upgrade org.apache.cxf:cxf-core to 3.2.1 or later
   • Upgrade org.apache.cxf:cxf-core to 3.1.14 or later
   • Upgrade org.apache.cxf:cxf-core to 3.0.16 or later