Affected versions
Red HatRed Hat Fuse 7/cxf-core
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to Apache CXF 4.2.3 or 4.1.8 or 3.6.12 which fixes this problem by imposing a default attachment size limit of 50mb.
A flaw was found in Apache CXF. This vulnerability allows a remote attacker to trigger a Denial of Service (DoS) by sending excessively large attachments. The affected component lacks a default maximum attachment size limit, enabling an attacker to consume system resources and disrupt service availability.

