DoS vulnerabilities persist in ESAPI file uploads despite remediation of CVE-2023-24998

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact ESAPI 2.5.2.0 and later addressed the DoS vulnerability described in CVE-2023-24998, which Apache Commons FileUpload 1.5 attempted to remediate. But while writing up a new security bulletin regarding the impact on the affected ESAPI HTTPUtilities.getFileUploads methods (or more specifically those methods in the DefaultHTTPUtilities implementation class), I realized that a DoS vulnerability still persists in ESAPI and for that matter in Apache Commons FileUpload as well. Related to CVE-2023-24998 Patches ESAPI 2.5.2.0 or later. Workarounds - See the 'Solutions' section of Security Bulletin 11, in the References section. If you are not using ESAPI file uploads, see also the 'Workarounds' section. - Deploy an external WAF or other suitable DoS protection. - Add additional defenses to your code using HTTPUtilities.getFileUpload, such as requiring prior authentication, restricting how many / much content can be uploaded per user per day or per hour, etc. (It is the opinion of the…

Published by the source

27 Oct 2023, 21:55 UTC

Last modified by the source

23 Jan 2024, 08:03 UTC

Source last checked

26 Oct 2026, 16:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7c2q-5qmr-v76q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7c2q-5qmr-v76q

Advisory: DoS vulnerabilities persist in ESAPI file uploads despite remediation of CVE-2023-24998
IDs: GHSA-7c2q-5qmr-v76q
Record: https://patchnext.com/advisories/ghsa-7c2q-5qmr-v76q (revision 1, source checked 26 Oct 2026, 16:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.owasp.esapi:esapi 2.5.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.owasp.esapi:esapi: affected < 2.5.2.0; fixed in 2.5.2.0

## Suggested inspection (read-only)
- Maven org.owasp.esapi:esapi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.owasp.esapi:esapi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7c2q-5qmr-v76q (GitHub-reviewed advisory GHSA-7c2q-5qmr-v76q lists affected ranges: Maven org.owasp.esapi:esapi >=0 <2.5.2.0)

Commands are suggestions: review each one before running it.