LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12624: Apache CXF supports sending and receiving attachments via either the JAX-WS or JAX-RS specifications.

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Apache CXF web services that accept message attachments can be forced into a denial-of-service condition by specially crafted attachment headers. The issue affects both JAX-WS and JAX-RS services in older CXF versions. Apache added a default header-size rejection limit in fixed releases. Exposure is likely where Apache CXF is used for SOAP or REST services with attachment handling enabled, especially internet-facing service providers. Systems not using CXF, or already on 3.1.14, 3.2.1, or later, are not indicated as affected by the provided sources. Prioritize remediation for externally reachable CXF services because the impact is service downtime. If CXF is internal-only or unused for attachments, handle through normal patch cycles after confirming exposure. Mitigation focus: Upgrade Apache CXF to 3.1.14, 3.2.1, or later supported releases.; Apply relevant Red Hat errata if CXF is consumed through Red Hat packages.; Verify attachment-max-header-size is enabled and appropriate for production workloads..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-12624 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache CXFprior to 3.1.14, 3.2.x prior to 3.2.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.