# CVE-2024-53299: Apache Wicket: An attacker can intentionally trigger a memory leak

> An attacker can cause a denial of service in Apache Wicket by triggering a memory leak through multiple requests to server resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-9cxr-76pm-j3wf

## What is CVE-2024-53299?

CVE-2024-53299 is a medium-severity denial of service vulnerability in Apache Wicket, published on 23 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The request handling in the core in Apache Wicket 7.0.0 on any platform allows an attacker to create a DOS via multiple requests to server resources.
Users are recommended to upgrade to versions 9.19.0 or 10.3.0, which fixes this issue.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-53299?

6 open source packages ship an affected version, including org.apache.wicket:wicket-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.wicket:wicket-core` | Maven | From 10.0.0 | 10.3.0 |
| `org.apache.wicket:wicket-core` | Maven | From 10.0.0 | 10.3.0 |
| `org.apache.wicket:wicket-core` | Maven | From 7.0.0 | 8.17.0 |
| `org.apache.wicket:wicket-core` | Maven | From 7.0.0 | 8.17.0 |
| `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M1 | 9.19.0 |
| `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M1 | 9.19.0 |

Products: Apache Wicket.

## How do I fix CVE-2024-53299?

Upgrade org.apache.wicket:wicket-core to a fixed version for your release line: 10.3.0, 8.17.0 or 9.19.0.

## Is CVE-2024-53299 being exploited?

There is no known exploitation of CVE-2024-53299 in the wild and no public exploit code.

## Other vulnerabilities in Apache Wicket

- [CVE-2024-36522](https://insights.sbomify.com/CVE-2024-36522/): Apache Wicket: Remote code execution via XSLT injection (critical 9.8)
- [CVE-2026-40010](https://insights.sbomify.com/CVE-2026-40010/): Apache Wicket: possible session fixation using AuthenticatedWebSession (critical 9.1)
- [CVE-2016-6793](https://insights.sbomify.com/CVE-2016-6793/): Deserialization in n/a (critical 9.1)
- [CVE-2016-6806](https://insights.sbomify.com/CVE-2016-6806/): Apache Wicket vulnerable to CSRF attacks (high 8.8)
- [CVE-2026-71257](https://insights.sbomify.com/CVE-2026-71257/): Apache Wicket: Configured file upload limits are not enforced when the multipart request has already been parsed (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53299 and fix it if it is affected.

What it is: CVE-2024-53299 is a medium-severity denial of service vulnerability in Apache Wicket, published on 23 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53299 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.wicket:wicket-core (Maven): affected from 10.0.0; fixed in 10.3.0
- org.apache.wicket:wicket-core (Maven): affected from 10.0.0; fixed in 10.3.0
- org.apache.wicket:wicket-core (Maven): affected from 7.0.0; fixed in 8.17.0
- org.apache.wicket:wicket-core (Maven): affected from 7.0.0; fixed in 8.17.0
- org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M1; fixed in 9.19.0
- org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M1; fixed in 9.19.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53299/ (Markdown: https://insights.sbomify.com/CVE-2024-53299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53299
- OSV: https://osv.dev/vulnerability/CVE-2024-53299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53299/
Summaries are generated and may contain mistakes; the official description above is the record.