{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-8970 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-8970 is a high-severity vulnerability in n/a, published on 24 Mar 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-8970 and fix it if it is affected.\n\nWhat it is: CVE-2018-8970 is a high-severity vulnerability in n/a, published on 24 Mar 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-8970 in the wild and no public exploit code.\n\nAffected product: n/a. 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-8970/ (Markdown: https://insights.sbomify.com/CVE-2018-8970/index.md)","id":"CVE-2018-8970","markdown":"https://insights.sbomify.com/CVE-2018-8970/index.md","name":"CVE-2018-8970","record":{"aliases":["GHSA-7gr4-mrjx-cjx9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreSSL crypto library","requires_auth":"none","summary":"Man-in-the-middle attackers can bypass hostname verification in LibreSSL to spoof servers and obtain sensitive information via crafted certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libressl","vendor":"openbsd"}],"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":"The int_x509_param_set_hosts function in lib/libcrypto/x509/x509_vpm.c in LibreSSL 2.7.0 before 2.7.1 does not support a certain special case of a zero name length, which causes silent omission of hostname verification, and consequently allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate. NOTE: the LibreSSL documentation indicates that this special case is supported, but the BoringSSL documentation does not.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-03-25","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-03-25T11:22:47Z","kind":"github_poc","ref":"https://github.com/tiran/CVE-2018-8970","stars":1,"title":"Demo for https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8970"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2018-8970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2018-8971"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-8969"},"products":["n/a"],"published":"2018-03-24","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2023-35784","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-46880","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in LibreSSL","id":"CVE-2015-5334","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":7.5,"headline":"Denial of service in LibreSSL","id":"CVE-2015-5333","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2014-9424","kev_date_added":null,"published":"2014-12-29"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2019-25048","kev_date_added":null,"published":"2021-07-01"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can bypass hostname verification in LibreSSL to spoof servers and obtain sensitive information via crafted certificates.","url":"https://insights.sbomify.com/CVE-2018-8970/"}