Skip to content

Apache Commons FileUpload denial of service vulnerability

High severity GitHub Reviewed Published Feb 20, 2023 to the GitHub Advisory Database • Updated Apr 18, 2024

Package

maven commons-fileupload:commons-fileupload (Maven)

Affected versions

< 1.5

Patched versions

1.5
maven org.apache.tomcat.embed:tomcat-embed-core (Maven)
>= 10.1.0-M1, < 10.1.5
>= 11.0.0-M2, < 11.0.0-M5
>= 8.5.85, < 8.5.88
>= 9.0.0-M1, < 9.0.71
10.1.5
11.0.0-M5
8.5.88
9.0.71
maven org.apache.tomcat:tomcat-coyote (Maven)
>= 10.1.0-M1, < 10.1.5
>= 11.0.0-M2, < 11.0.0-M5
>= 8.5.85, < 8.5.88
>= 9.0.0-M1, < 9.0.71
10.1.5
11.0.0-M5
8.5.88
9.0.71

Description

Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads. Note that, like all of the file upload limits, the new configuration option (FileUploadBase#setFileCountMax) is not enabled by default and must be explicitly configured.

References

Published by the National Vulnerability Database Feb 20, 2023
Published to the GitHub Advisory Database Feb 20, 2023
Reviewed Feb 22, 2023
Last updated Apr 18, 2024

Severity

High

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
None
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:N/S:U/C:N/I:N/A:H

EPSS score

2.163%
(90th percentile)

Weaknesses

CVE ID

CVE-2023-24998

GHSA ID

GHSA-hfrx-6qgj-fp6c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.