{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-15698 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-15698 is a medium-severity vulnerability in Debian Debian Linux, published on 31 Jan 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-2017-15698 and fix it if it is affected.\n\nWhat it is: CVE-2017-15698 is a medium-severity vulnerability in Debian Debian Linux, published on 31 Jan 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-2017-15698 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-2017-15698/ (Markdown: https://insights.sbomify.com/CVE-2017-15698/index.md)","id":"CVE-2017-15698","markdown":"https://insights.sbomify.com/CVE-2017-15698/index.md","name":"CVE-2017-15698","record":{"aliases":["DEBIAN-CVE-2017-15698","DLA-1276-1","DSA-4118-1","GHSA-ppg5-72hh-9jj4","MGASA-2018-0150","UBUNTU-CVE-2017-15698"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Tomcat Native","requires_auth":"none","summary":"Attackers can bypass OCSP revocation checks in Apache Tomcat Native Connector by using long AIA fields, allowing revoked client certificates to be accepted.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"tomcat_native","vendor":"apache"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"When parsing the AIA-Extension field of a client certificate, Apache Tomcat Native Connector 1.2.0 to 1.2.14 and 1.1.23 to 1.1.34 did not correctly handle fields longer than 127 bytes. The result of the parsing error was to skip the OCSP check. It was therefore possible for client certificates that should have been rejected (if the OCSP check had been made) to be accepted. 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":"Security feature bypass in Apache Tomcat Native","id":"CVE-2017-15698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux"],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":10,"next":{"headline":"Denial of service in Apache Qpid Dispatch Router","id":"CVE-2017-15699"},"packages":[],"prev":{"headline":"Apache NiFi XSS issue in context path handling","id":"CVE-2017-15697"},"products":["Apache Tomcat Native"],"published":"2018-01-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-8019","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":7.4,"headline":"Auth bypass in Apache Tomcat Native","id":"CVE-2018-8020","kev_date_added":null,"published":"2018-07-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 bypass OCSP revocation checks in Apache Tomcat Native Connector by using long AIA fields, allowing revoked client certificates to be accepted.","url":"https://insights.sbomify.com/CVE-2017-15698/"}