Technical impact
Apache Wicket’s form‑less upload resource fails to honour limits configured in the application, allowing an attacker to supply arbitrarily large maxSize, fileMaxSize, or fileCountMax values. The server accepts the request without any ceiling, spooling data above the in‑memory threshold to the container’s temporary directory and finally copying file parts to the application’s upload folder. Because the parser accepts all data, a single request can consume unlimited disk or heap space, leading to performance degradation, crashes, or denial of service.
Affected Systems
The flaw exists in Apache Wicket versions 9.14.0 through 9.24.0 and 10.0.0 through 10.9.1. Those applications that use FileUploadToResourceField or mount FileUploadResourceReference are vulnerable. The issue does not impact the upload mechanisms that use FileUploadField or AjaxFileDropBehavior, nor does it affect the 8.x series.
Risk and Exploitability
The vulnerability has a CVSS score of 8.3 and no EPSS data is available. It is not listed in the CISA Known Exploited Vulnerabilities catalog. The resource is publicly accessible and carries no authorization annotation, so an unauthenticated attacker can reach the endpoint via HTTP. By sending a crafted payload that sets a very large maxSize (and omitting fileMaxSize and fileCountMax), the attacker can make the server allocate as much memory and disk space as desired, causing an availability loss.