{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-3190 in the wild and no public exploit code.","fix":"Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 5.5.34, 6.0.34 or 7.0.21.","what":"CVE-2011-3190 is a high-severity authentication bypass vulnerability in Apache Tomcat, published on 31 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-3190 and fix it if it is affected.\n\nWhat it is: CVE-2011-3190 is a high-severity authentication bypass vulnerability in Apache Tomcat, published on 31 Aug 2011. 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-2011-3190 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tomcat:tomcat (Maven): affected from 5.0.0; fixed in 5.5.34\n- org.apache.tomcat:tomcat (Maven): affected from 5.0.0; fixed in 5.5.34\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.34\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.34\n- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.21\n- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.21\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-2011-3190/ (Markdown: https://insights.sbomify.com/CVE-2011-3190/index.md)","id":"CVE-2011-3190","markdown":"https://insights.sbomify.com/CVE-2011-3190/index.md","name":"CVE-2011-3190","record":{"aliases":["GHSA-c38m-v4m2-524v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Tomcat","requires_auth":"none","summary":"Remote attackers can bypass authentication and access sensitive information by spoofing AJP requests in Apache Tomcat.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tomcat","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Certain AJP protocol connector implementations in Apache Tomcat 7.0.0 through 7.0.20, 6.0.0 through 6.0.33, 5.5.0 through 5.5.33, and possibly other versions allow remote attackers to spoof AJP requests, bypass authentication, and obtain sensitive information by causing the connector to interpret a request body as a new request.","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 Allows Remote Attackers to Spoof AJP Requests","id":"CVE-2011-3190","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:tomcat","products":["apache:tomcat"],"type":"auth_bypass","year":"2011"},"n_packages":6,"n_references":25,"next":{"headline":"Integer overflow in n/a","id":"CVE-2011-3191"},"packages":[{"ecosystem":"Maven","fixed":["5.5.34"],"introduced":["5.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c38m-v4m2-524v"},{"ecosystem":"Maven","fixed":["5.5.34"],"introduced":["5.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c38m-v4m2-524v"},{"ecosystem":"Maven","fixed":["6.0.34"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c38m-v4m2-524v"},{"ecosystem":"Maven","fixed":["6.0.34"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c38m-v4m2-524v"},{"ecosystem":"Maven","fixed":["7.0.21"],"introduced":["7.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c38m-v4m2-524v"},{"ecosystem":"Maven","fixed":["7.0.21"],"introduced":["7.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c38m-v4m2-524v"}],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2011-3189"},"products":["n/a"],"published":"2011-08-31","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can bypass authentication and access sensitive information by spoofing AJP requests in Apache Tomcat.","url":"https://insights.sbomify.com/CVE-2011-3190/"}