{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-2009 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-2009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-2009 is a medium-severity vulnerability in Apache Tomcat, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-2009 and fix it if it is affected.\n\nWhat it is: CVE-2002-2009 is a medium-severity vulnerability in Apache Tomcat, published on 14 Jul 2005. 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-2002-2009 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tomcat:tomcat (Maven): affected from 4.0.0 up to 4.0.1; no fix listed\n- org.apache.tomcat:tomcat (Maven): affected from 4.0.0 up to 4.0.1; no fix listed\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-2002-2009/ (Markdown: https://insights.sbomify.com/CVE-2002-2009/index.md)","id":"CVE-2002-2009","markdown":"https://insights.sbomify.com/CVE-2002-2009/index.md","name":"CVE-2002-2009","record":{"aliases":["GHSA-r6cf-cr44-m8rr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Tomcat","requires_auth":"none","summary":"Remote attackers can obtain the web root path via crafted HTTP requests for JSP files, leaking sensitive pathname information in error messages.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tomcat","vendor":"apache"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Apache Tomcat 4.0.1 allows remote attackers to obtain the web root path via HTTP requests for JSP files preceded by (1) +/, (2) \u003e/, (3) \u003c/, and (4) %20/, which leaks the pathname in an error message.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache Tomcat Leaks Pathname Information via Error Message","id":"CVE-2002-2009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:tomcat","products":["apache:tomcat"],"type":"information_disclosure","year":"2002"},"n_packages":2,"n_references":8,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-2010"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["4.0.0"],"last_affected":["4.0.1"],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-r6cf-cr44-m8rr"},{"ecosystem":"Maven","fixed":[],"introduced":["4.0.0"],"last_affected":["4.0.1"],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-r6cf-cr44-m8rr"}],"prev":{"headline":"Apache Tomcat Leaks Information via Error Message","id":"CVE-2002-2008"},"products":["n/a"],"published":"2005-07-14","related":[{"cvss_score":10,"headline":"Apache Tomcat Path Equivalence","id":"CVE-2025-24813","kev_date_added":"2025-04-01","published":"2025-03-10"},{"cvss_score":9.8,"headline":"Apache Tomcat Remote Code Execution","id":"CVE-2016-8735","kev_date_added":"2023-05-12","published":"2017-04-06"},{"cvss_score":8.1,"headline":"Apache Tomcat Remote Code Execution","id":"CVE-2017-12617","kev_date_added":"2022-03-25","published":"2017-10-03"},{"cvss_score":8.1,"headline":"Apache Tomcat on Windows Remote Code Execution","id":"CVE-2017-12615","kev_date_added":"2022-03-25","published":"2017-09-19"},{"cvss_score":7.5,"headline":"Apache Tomcat Missing Encryption of Sensitive Data","id":"CVE-2026-34486","kev_date_added":"2026-08-04","published":"2026-04-09"},{"cvss_score":9.8,"headline":"Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix incomplete","id":"CVE-2026-65637","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.8,"headline":"Apache Tomcat: Limited replay attack possible with DIGEST authentication","id":"CVE-2026-65905","kev_date_added":null,"published":"2026-08-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can obtain the web root path via crafted HTTP requests for JSP files, leaking sensitive pathname information in error messages.","url":"https://insights.sbomify.com/CVE-2002-2009/"}