{"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-2204 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.33 or 7.0.19.","what":"CVE-2011-2204 is a low-severity vulnerability in Apache Tomcat, published on 29 Jun 2011. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-2204 and fix it if it is affected.\n\nWhat it is: CVE-2011-2204 is a low-severity vulnerability in Apache Tomcat, published on 29 Jun 2011. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2011-2204 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tomcat:tomcat (Maven): affected from 5.5.0; fixed in 5.5.34\n- org.apache.tomcat:tomcat (Maven): affected from 5.5.0; fixed in 5.5.34\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.33\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.33\n- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.19\n- org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.19\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-2204/ (Markdown: https://insights.sbomify.com/CVE-2011-2204/index.md)","id":"CVE-2011-2204","markdown":"https://insights.sbomify.com/CVE-2011-2204/index.md","name":"CVE-2011-2204","record":{"aliases":["GHSA-c57p-3v2g-w9rg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Apache Tomcat","requires_auth":"none","summary":"Local attackers can read log files to obtain sensitive passwords when MemoryUserDatabase is enabled and JMX errors occur.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tomcat","vendor":"apache"}],"cvss":{"score":1.9,"severity":"low","source":"nvd","vector":"AV:L/AC:M/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.17, when the MemoryUserDatabase is used, creates log entries containing passwords upon encountering errors in JMX user creation, which allows local users to obtain sensitive information by reading a log 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":"Insertion of Sensitive Information into Log File in Apache Tomcat","id":"CVE-2011-2204","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:tomcat","products":["apache:tomcat"],"type":"information_disclosure","year":"2011"},"n_packages":6,"n_references":29,"next":{"headline":"Denial of service in n/a","id":"CVE-2011-2205"},"packages":[{"ecosystem":"Maven","fixed":["5.5.34"],"introduced":["5.5.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c57p-3v2g-w9rg"},{"ecosystem":"Maven","fixed":["5.5.34"],"introduced":["5.5.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c57p-3v2g-w9rg"},{"ecosystem":"Maven","fixed":["6.0.33"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c57p-3v2g-w9rg"},{"ecosystem":"Maven","fixed":["6.0.33"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c57p-3v2g-w9rg"},{"ecosystem":"Maven","fixed":["7.0.19"],"introduced":["7.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-c57p-3v2g-w9rg"},{"ecosystem":"Maven","fixed":["7.0.19"],"introduced":["7.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-c57p-3v2g-w9rg"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2011-2203"},"products":["n/a"],"published":"2011-06-29","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":"Local attackers can read log files to obtain sensitive passwords when MemoryUserDatabase is enabled and JMX errors occur.","url":"https://insights.sbomify.com/CVE-2011-2204/"}