Skip to content

Potential DOS attack due to unrestricted attachment count in messages

Moderate severity GitHub Reviewed Published Nov 8, 2019 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.cxf:apache-cxf (Maven)

Affected versions

< 3.2.11
>= 3.3.0, < 3.3.4

Patched versions

3.2.11
3.3.4
maven org.apache.cxf:cxf (Maven)
< 3.2.11
>= 3.3.0, < 3.3.4
3.2.11
3.3.4

Description

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

References

Published by the National Vulnerability Database Nov 6, 2019
Reviewed Nov 7, 2019
Published to the GitHub Advisory Database Nov 8, 2019
Last updated Feb 1, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(87th percentile)

Weaknesses

CVE ID

CVE-2019-12406

GHSA ID

GHSA-58p8-9g59-q2hr

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.