{"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-2010-4312 in the wild and no public exploit code.","fix":"Upgrade org.apache.tomcat:tomcat to 6.0.35 or later.","what":"CVE-2010-4312 is a medium-severity vulnerability in Apache Tomcat, published on 26 Nov 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2010-4312 and fix it if it is affected.\n\nWhat it is: CVE-2010-4312 is a medium-severity vulnerability in Apache Tomcat, published on 26 Nov 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2010-4312 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.35\n- org.apache.tomcat:tomcat (Maven): affected from 6.0.0; fixed in 6.0.35\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-2010-4312/ (Markdown: https://insights.sbomify.com/CVE-2010-4312/index.md)","id":"CVE-2010-4312","markdown":"https://insights.sbomify.com/CVE-2010-4312/index.md","name":"CVE-2010-4312","record":{"aliases":["GHSA-pvjh-7h8q-q56r"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web server","requires_auth":"none","summary":"Attackers can hijack user sessions via script access to cookies because the default configuration lacks the HTTPOnly flag.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tomcat","vendor":"apache"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-16","name":null}],"description":"The default configuration of Apache Tomcat 6.x does not include the HTTPOnly flag in a Set-Cookie header, which makes it easier for remote attackers to hijack a session via script access to a cookie.","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 has cookies without HTTPOnly flag in Set-Cookie header","id":"CVE-2010-4312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:tomcat","products":["apache:tomcat"],"type":"security_feature_bypass","year":"2010"},"n_packages":2,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2010-4313"},"packages":[{"ecosystem":"Maven","fixed":["6.0.35"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":null,"source":"GHSA-pvjh-7h8q-q56r"},{"ecosystem":"Maven","fixed":["6.0.35"],"introduced":["6.0.0"],"last_affected":[],"package":"org.apache.tomcat:tomcat","purl":"pkg:maven/org.apache.tomcat/tomcat","source":"GHSA-pvjh-7h8q-q56r"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2010-4311"},"products":["n/a"],"published":"2010-11-26","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-07","vendors":["n/a"]},"summary":"Attackers can hijack user sessions via script access to cookies because the default configuration lacks the HTTPOnly flag.","url":"https://insights.sbomify.com/CVE-2010-4312/"}