CVE-2014-0043 json
Apache Wicket allows attackers to check for third-party libraries
published 2017-10-02 9 y ago modified 2026-06-17 4 mo ago also GHSA-244g-8368-6wr9 , EUVD-2014-0140
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.wicket:wicket-core 1.5.11, 6.14.0
Exploit prediction
3.01% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.wicket:wicket-core | >=1.5-RC1, <1.5.11 >=6.0.0-beta1, <6.14.0 |
1.5.11 6.14.0 |
Affected products
- Apache Software Foundation Apache Wicket
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
lists.apache.org
/thread.html/d95e962f2f059a09f5abf7086c3f4ed22d2ae2c21499d0de95d4435d%401392986987%40%3Cannounce.wicket.apache
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2014-0043
advisory
-
github.com
/apache/wicket
package
-
lists.apache.org
/thread.html/d95e962f2f059a09f5abf7086c3f4ed22d2ae2c21499d0de95d4435d@1392986987@%3Cannounce.wicket.apache.org
web
Sources
- CVE List CVE-2014-0043
- GitHub Advisory GHSA-244g-8368-6wr9
- NVD CVE-2014-0043
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.