{"answers":{"affected":"5 open source packages ship an affected version, including hyper. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18587 in the wild and no public exploit code.","fix":"Upgrade hyper to a fixed version for your release line: 0.9.18 or 0.10.2.","what":"CVE-2017-18587 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-18587 and fix it if it is affected.\n\nWhat it is: CVE-2017-18587 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-18587 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hyper (crates.io): affected all versions; fixed in 0.9.18\n- hyper (crates.io): affected all versions; fixed in 0.9.18\n- hyper (crates.io): affected from 0.0.0-0; fixed in 0.9.18, 0.10.2\n- hyper (crates.io): affected from 0.10.0; fixed in 0.10.2\n- hyper (crates.io): affected from 0.10.0; fixed in 0.10.2\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-18587/ (Markdown: https://insights.sbomify.com/CVE-2017-18587/index.md)","id":"CVE-2017-18587","markdown":"https://insights.sbomify.com/CVE-2017-18587/index.md","name":"CVE-2017-18587","record":{"aliases":["GHSA-q89x-f52w-6hj2","RUSTSEC-2017-0002"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust HTTP library","requires_auth":"none","summary":"The hyper crate mishandles newlines in headers, potentially allowing HTTP request smuggling or header injection attacks.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hyper","vendor":"hyper"}],"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-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"An issue was discovered in the hyper crate before 0.9.18 for Rust. It mishandles newlines in headers.","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":"Headers containing newline characters can split messages in hyper","id":"CVE-2017-18587","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2017"},"n_packages":5,"n_references":1,"next":{"headline":"Improper Certificate Validation in security-framework","id":"CVE-2017-18588"},"packages":[{"ecosystem":"crates.io","fixed":["0.9.18"],"introduced":["0"],"last_affected":[],"package":"hyper","purl":null,"source":"GHSA-q89x-f52w-6hj2"},{"ecosystem":"crates.io","fixed":["0.9.18"],"introduced":["0"],"last_affected":[],"package":"hyper","purl":"pkg:cargo/hyper","source":"GHSA-q89x-f52w-6hj2"},{"ecosystem":"crates.io","fixed":["0.9.18","0.10.2"],"introduced":["0.0.0-0","0.10.0"],"last_affected":[],"package":"hyper","purl":"pkg:cargo/hyper","source":"RUSTSEC-2017-0002"},{"ecosystem":"crates.io","fixed":["0.10.2"],"introduced":["0.10.0"],"last_affected":[],"package":"hyper","purl":null,"source":"GHSA-q89x-f52w-6hj2"},{"ecosystem":"crates.io","fixed":["0.10.2"],"introduced":["0.10.0"],"last_affected":[],"package":"hyper","purl":"pkg:cargo/hyper","source":"GHSA-q89x-f52w-6hj2"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-18586"},"products":["n/a"],"published":"2019-08-26","related":[{"cvss_score":9.8,"headline":"HTTP Request Smuggling in hyper","id":"CVE-2020-35863","kev_date_added":null,"published":"2020-12-31"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-31394","kev_date_added":null,"published":"2023-02-21"},{"cvss_score":5.9,"headline":"Integer Overflow in Chunked Transfer-Encoding","id":"CVE-2021-32714","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":4.8,"headline":"Multiple Transfer-Encoding headers misinterprets request payload","id":"CVE-2021-21299","kev_date_added":null,"published":"2021-02-11"},{"cvss_score":4.8,"headline":"HTTPS MitM vulnerability due to lack of hostname verification","id":"CVE-2016-10932","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":3.1,"headline":"Lenient Parsing of Content-Length Header When Prefixed with Plus Sign","id":"CVE-2021-32715","kev_date_added":null,"published":"2021-07-07"}],"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":"The hyper crate mishandles newlines in headers, potentially allowing HTTP request smuggling or header injection attacks.","url":"https://insights.sbomify.com/CVE-2017-18587/"}