{"answers":{"affected":"3 open source packages ship an affected version, including security-framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18588 in the wild and no public exploit code.","fix":"Upgrade security-framework to 0.1.12 or later.","what":"CVE-2017-18588 is a medium-severity vulnerability in n/a, published on 26 Aug 2019. 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-18588 and fix it if it is affected.\n\nWhat it is: CVE-2017-18588 is a medium-severity vulnerability in n/a, published on 26 Aug 2019. 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-18588 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- security-framework (crates.io): affected all versions; fixed in 0.1.12\n- security-framework (crates.io): affected all versions; fixed in 0.1.12\n- security-framework (crates.io): affected from 0.0.0-0; fixed in 0.1.12\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-18588/ (Markdown: https://insights.sbomify.com/CVE-2017-18588/index.md)","id":"CVE-2017-18588","markdown":"https://insights.sbomify.com/CVE-2017-18588/index.md","name":"CVE-2017-18588","record":{"aliases":["GHSA-jqqr-c2r2-9cvr","RUSTSEC-2017-0003"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust security-framework crate","requires_auth":"none","summary":"Attackers can bypass certificate hostname verification in Rust applications using custom root certificates, enabling man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"security-framework","vendor":"security-framework_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in the security-framework crate before 0.1.12 for Rust. Hostname verification for certificates does not occur if ClientBuilder uses custom root certificates.","ecosystems":["crates.io"],"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":"Improper Certificate Validation in security-framework","id":"CVE-2017-18588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":3,"n_references":1,"next":{"headline":"Improper Input Validation in cookie","id":"CVE-2017-18589"},"packages":[{"ecosystem":"crates.io","fixed":["0.1.12"],"introduced":["0"],"last_affected":[],"package":"security-framework","purl":null,"source":"GHSA-jqqr-c2r2-9cvr"},{"ecosystem":"crates.io","fixed":["0.1.12"],"introduced":["0"],"last_affected":[],"package":"security-framework","purl":"pkg:cargo/security-framework","source":"GHSA-jqqr-c2r2-9cvr"},{"ecosystem":"crates.io","fixed":["0.1.12"],"introduced":["0.0.0-0"],"last_affected":[],"package":"security-framework","purl":"pkg:cargo/security-framework","source":"RUSTSEC-2017-0003"}],"prev":{"headline":"Headers containing newline characters can split messages in hyper","id":"CVE-2017-18587"},"products":["n/a"],"published":"2019-08-26","related":[],"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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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-05","vendors":["n/a"]},"summary":"Attackers can bypass certificate hostname verification in Rust applications using custom root certificates, enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2017-18588/"}