{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-8019 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-8019 is a high-severity authentication bypass vulnerability in Debian Debian Linux, published on 31 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-8019 and fix it if it is affected.\n\nWhat it is: CVE-2018-8019 is a high-severity authentication bypass vulnerability in Debian Debian Linux, published on 31 Jul 2018. 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-2018-8019 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2018-8019/ (Markdown: https://insights.sbomify.com/CVE-2018-8019/index.md)","id":"CVE-2018-8019","markdown":"https://insights.sbomify.com/CVE-2018-8019/index.md","name":"CVE-2018-8019","record":{"aliases":["DEBIAN-CVE-2018-8019","GHSA-w5fc-h82j-vq6w","UBUNTU-CVE-2018-8019"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Tomcat Native","requires_auth":"none","summary":"Attackers can authenticate using revoked client certificates when OCSP is enabled, bypassing mutual TLS security controls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"tomcat_native","vendor":"apache"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"When using an OCSP responder Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 did not correctly handle invalid responses. This allowed for revoked client certificates to be incorrectly identified. It was therefore possible for users to authenticate with revoked certificates when using mutual TLS. Users not using OCSP checks are not affected by this vulnerability.","ecosystems":[],"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":"Auth bypass in Apache Tomcat Native","id":"CVE-2018-8019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux"],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":10,"next":{"headline":"Auth bypass in Apache Tomcat Native","id":"CVE-2018-8020"},"packages":[],"prev":{"headline":"Code execution via deserialization in org.apache.ignite:ignite-core","id":"CVE-2018-8018"},"products":["Apache Tomcat Native"],"published":"2018-07-31","related":[{"cvss_score":9.1,"headline":"Apache Tomcat Native: Insecure OpenSSL options enabled","id":"CVE-2026-86246","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":7.5,"headline":"Apache Tomcat Native: DoS via TLS handshake","id":"CVE-2026-86243","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":7.4,"headline":"Apache Tomcat Native: Client certificate requirements can be down-graded","id":"CVE-2026-86247","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":7.4,"headline":"Auth bypass in Apache Tomcat Native","id":"CVE-2018-8020","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":5.9,"headline":"Security feature bypass in Apache Tomcat Native","id":"CVE-2017-15698","kev_date_added":null,"published":"2018-01-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can authenticate using revoked client certificates when OCSP is enabled, bypassing mutual TLS security controls.","url":"https://insights.sbomify.com/CVE-2018-8019/"}