CVE-2024-53299
MEDIUMCVE-2024-53299 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.apache.wicket:wicket-core. O3 Security confirms whether CVE-2024-53299 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Wicket: An attacker can intentionally trigger a memory leak
Real-World Exposure
org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.wicket:wicket-core | ≥ 7.0.0&&< 8.17.0 | 8.17.0 |
| ☕Maven | org.apache.wicket:wicket-core | ≥ 10.0.0&&< 10.3.0 | 10.3.0 |
| ☕Maven | org.apache.wicket:wicket-core | ≥ 9.0.0-M1&&< 9.19.0 | 9.19.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.wicket:wicket-core to 8.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-53299 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-53299 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-53299. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-53299 in your dependencies?
O3 detects CVE-2024-53299 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.