{"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-2013-4444 in the wild and no public exploit code.","fix":"Upgrade org.apache.tomcat:tomcat to 7.0.40 or later.","what":"CVE-2013-4444 is a medium-severity vulnerability in Apache Tomcat, published on 12 Sep 2014. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-4444 and fix it if it is affected.\n\nWhat it is: CVE-2013-4444 is a medium-severity vulnerability in Apache Tomcat, published on 12 Sep 2014. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-4444 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tomcat:tomcat (Maven): affected from 7.0; fixed in 7.0.40\n- org.apache.tomcat:tomcat (Maven): affected from 7.0; fixed in 7.0.40\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-2013-4444/ (Markdown: https://insights.sbomify.com/CVE-2013-4444/index.md)","id":"CVE-2013-4444","markdown":"https://insights.sbomify.com/CVE-2013-4444/index.md","name":"CVE-2013-4444","record":{"aliases":["GHSA-h6c8-x5r3-pm88"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Tomcat","requires_auth":"high_privilege","summary":"Remote attackers can execute arbitrary code by uploading a JSP file in Apache Tomcat when specific JMX configurations are enabled.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tomcat","vendor":"apache"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Unrestricted file upload vulnerability in Apache Tomcat 7.x before 7.0.40, in certain situations involving outdated java.io.File code and a custom JMX configuration, allows remote attackers to execute arbitrary code by uploading and accessing a JSP file.","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":true,"headline":"Apache Tomcat Unrestricted file upload vulnerability","id":"CVE-2013-4444","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:tomcat","products":["apache:tomcat"],"type":"file_upload","year":"2013"},"n_packages":2,"n_references":10,"next":{"headline":"Auth bypass in n/a","id":"CVE-2013-4445"},"packages":[{"ecosystem":"Maven","fixed":["7.0.40"],"introduced":["7.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-h6c8-x5r3-pm88"},{"ecosystem":"Maven","fixed":["7.0.40"],"introduced":["7.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-h6c8-x5r3-pm88"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2013-4443"},"products":["n/a"],"published":"2014-09-12","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-09","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by uploading a JSP file in Apache Tomcat when specific JMX configurations are enabled.","url":"https://insights.sbomify.com/CVE-2013-4444/"}