{"answers":{"affected":"4 open source packages ship an affected version, including org.apache.wicket:wicket-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-0043 in the wild and no public exploit code.","fix":"Upgrade org.apache.wicket:wicket-core to a fixed version for your release line: 1.5.11 or 6.14.0.","what":"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."},"fix_prompt":"Check this codebase for CVE-2014-0043 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2014-0043 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.wicket:wicket-core (Maven): affected from 1.5-RC1; fixed in 1.5.11\n- org.apache.wicket:wicket-core (Maven): affected from 1.5-RC1; fixed in 1.5.11\n- org.apache.wicket:wicket-core (Maven): affected from 6.0.0-beta1; fixed in 6.14.0\n- org.apache.wicket:wicket-core (Maven): affected from 6.0.0-beta1; fixed in 6.14.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2014-0043/ (Markdown: https://insights.sbomify.com/CVE-2014-0043/index.md)","id":"CVE-2014-0043","markdown":"https://insights.sbomify.com/CVE-2014-0043/index.md","name":"CVE-2014-0043","record":{"aliases":["GHSA-244g-8368-6wr9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web framework","requires_auth":"none","summary":"Attackers can determine if specific vulnerable libraries are present in the application classpath by probing special URLs, aiding targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"wicket","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2022-07-27","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-07-27T14:43:54Z","kind":"github_poc","ref":"https://github.com/JJK96/JavaClasspathEnum","stars":0,"title":"Java classpath enumeration, focussed on CVE-2014-0043 for Apache Wicket 6.x"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Wicket allows attackers to check for third-party libraries","id":"CVE-2014-0043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":4,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2014-0044"},"packages":[{"ecosystem":"Maven","fixed":["1.5.11"],"introduced":["1.5-RC1"],"last_affected":[],"package":"org.apache.wicket:wicket-core","purl":null,"source":"GHSA-244g-8368-6wr9"},{"ecosystem":"Maven","fixed":["1.5.11"],"introduced":["1.5-RC1"],"last_affected":[],"package":"org.apache.wicket:wicket-core","purl":"pkg:maven/org.apache.wicket/wicket-core","source":"GHSA-244g-8368-6wr9"},{"ecosystem":"Maven","fixed":["6.14.0"],"introduced":["6.0.0-beta1"],"last_affected":[],"package":"org.apache.wicket:wicket-core","purl":null,"source":"GHSA-244g-8368-6wr9"},{"ecosystem":"Maven","fixed":["6.14.0"],"introduced":["6.0.0-beta1"],"last_affected":[],"package":"org.apache.wicket:wicket-core","purl":"pkg:maven/org.apache.wicket/wicket-core","source":"GHSA-244g-8368-6wr9"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2014-0042"},"products":["Apache Wicket"],"published":"2017-10-02","related":[{"cvss_score":9.8,"headline":"Apache Wicket: Remote code execution via XSLT injection","id":"CVE-2024-36522","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":9.1,"headline":"Apache Wicket: possible session fixation using AuthenticatedWebSession","id":"CVE-2026-40010","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":9.1,"headline":"Deserialization in n/a","id":"CVE-2016-6793","kev_date_added":null,"published":"2017-07-14"},{"cvss_score":8.8,"headline":"Apache Wicket vulnerable to CSRF attacks","id":"CVE-2016-6806","kev_date_added":null,"published":"2017-10-02"},{"cvss_score":7.5,"headline":"Apache Wicket: Configured file upload limits are not enforced when the multipart request has already been parsed","id":"CVE-2026-71257","kev_date_added":null,"published":"2026-08-31"},{"cvss_score":7.5,"headline":"Apache Wicket: crafted URLs can bypass PackageResourceGuard","id":"CVE-2026-43646","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.5,"headline":"DNS proxy and possible amplification attack","id":"CVE-2021-23937","kev_date_added":null,"published":"2021-05-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can determine if specific vulnerable libraries are present in the application classpath by probing special URLs, aiding targeted attacks.","url":"https://insights.sbomify.com/CVE-2014-0043/"}