# CVE-2014-0043: Apache Wicket allows attackers to check for third-party libraries

> Attackers can determine if specific vulnerable libraries are present in the application classpath by probing special URLs, aiding targeted attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-244g-8368-6wr9

## What is CVE-2014-0043?

CVE-2014-0043 is a medium-severity vulnerability in Apache Wicket, published on 2 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Apache Wicket 1.5.10 or 6.13.0, by issuing requests to special urls handled by Wicket, it is possible to check for the existence of particular classes in the classpath and thus check whether a third party library with a known security vulnerability is in use.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-0043?

4 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 1.5-RC1 | 1.5.11 |
| `org.apache.wicket:wicket-core` | Maven | From 1.5-RC1 | 1.5.11 |
| `org.apache.wicket:wicket-core` | Maven | From 6.0.0-beta1 | 6.14.0 |
| `org.apache.wicket:wicket-core` | Maven | From 6.0.0-beta1 | 6.14.0 |

Products: Apache Wicket.

## How do I fix CVE-2014-0043?

Upgrade org.apache.wicket:wicket-core to a fixed version for your release line: 1.5.11 or 6.14.0.

## Is CVE-2014-0043 being exploited?

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

Public exploit code:

- Java classpath enumeration, focussed on CVE-2014-0043 for Apache Wicket 6.x (github_poc): https://github.com/JJK96/JavaClasspathEnum

## 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-2014-0043 and fix it if it is affected.

What it is: CVE-2014-0043 is a medium-severity vulnerability in Apache Wicket, published on 2 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0043 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.wicket:wicket-core (Maven): affected from 1.5-RC1; fixed in 1.5.11
- org.apache.wicket:wicket-core (Maven): affected from 1.5-RC1; fixed in 1.5.11
- org.apache.wicket:wicket-core (Maven): affected from 6.0.0-beta1; fixed in 6.14.0
- org.apache.wicket:wicket-core (Maven): affected from 6.0.0-beta1; fixed in 6.14.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-2014-0043/ (Markdown: https://insights.sbomify.com/CVE-2014-0043/index.md)
```

## Sources

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

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