Skip to content
Fencer Intel
medium 6.5

CVE-2019-12406 json

Potential DOS attack due to unrestricted attachment count in messages

published 7y ago modified 4mo ago also GHSA-58p8-9g59-q2hr , EUVD-2019-0728

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.3%
EPSS 6.3% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

Apache CXF before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property "attachment-max-count".

Patch / fix

  • maven org.apache.cxf:cxf 3.2.11, 3.3.4
  • maven org.apache.cxf:apache-cxf 3.2.11, 3.3.4
  • apache cxf 3.2.11, 3.3.4

Is CVE-2019-12406 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-12406 updated cvss 6.5

cxf: does not restrict the number of message attachments

  • Red Hat BPM Suite 6 cxf, cxf-core Red Hat JBoss BRMS 6 cxf, cxf-core Red Hat JBoss Fuse 6 cxf-core
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Application Runtimes cxf-core
    affected: no fix available
  • Red Hat Decision Manager 7
    fixed: vendor fix RHSA-2020:3196
  • Red Hat Fuse 7.8.0
    fixed: vendor fix RHSA-2020:5568
  • Red Hat Process Automation 7
    fixed: vendor fix RHSA-2020:3197
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2020:2067
  • Red Hat JBoss Enterprise Application Platform 7 cxf, cxf-core Red Hat Single Sign-On 7 cxf-core Red Hat support for Spring Boot cxf-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.26% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.cxf:cxf
<3.2.11
>=3.3.0, <3.3.4
3.2.11
3.3.4
maven org.apache.cxf:apache-cxf
<3.2.11
>=3.3.0, <3.3.4
3.2.11
3.3.4

Affected products

  • n/a Apache CXF

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.