{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000099 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-1000099 is a medium-severity vulnerability in Haxx Libcurl, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-1000099 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000099 is a medium-severity vulnerability in Haxx Libcurl, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-1000099 in the wild and no public exploit code.\n\nAffected product: Haxx Libcurl. 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-1000099/ (Markdown: https://insights.sbomify.com/CVE-2017-1000099/index.md)","id":"CVE-2017-1000099","markdown":"https://insights.sbomify.com/CVE-2017-1000099/index.md","name":"CVE-2017-1000099","record":{"aliases":["ALPINE-CVE-2017-1000099","CLEANSTART-2026-DV20769","CURL-CVE-2017-1000099","GHSA-q937-ph5c-26qf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"libcurl library","requires_auth":"none","summary":"An attacker can read uninitialized heap memory via file:// URL requests in libcurl, potentially exposing sensitive private data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libcurl","vendor":"haxx"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory.","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":"Information disclosure in n/a","id":"CVE-2017-1000099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"haxx:libcurl","products":["haxx:libcurl"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-1000100"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-1000098"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":7.5,"headline":"freeing stack buffer in utf8asn1str","id":"CVE-2024-6197","kev_date_added":null,"published":"2024-07-24"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2017-1000254","kev_date_added":null,"published":"2017-10-06"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2016-7141","kev_date_added":null,"published":"2016-10-03"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2017-1000100","kev_date_added":null,"published":"2017-10-04"},{"cvss_score":6.3,"headline":"ASN.1 date parser overread","id":"CVE-2024-7264","kev_date_added":null,"published":"2024-07-31"},{"cvss_score":4.8,"headline":"Security feature bypass in curl","id":"CVE-2017-7468","kev_date_added":null,"published":"2018-07-16"}],"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-08-05","vendors":["n/a"]},"summary":"An attacker can read uninitialized heap memory via file:// URL requests in libcurl, potentially exposing sensitive private data.","url":"https://insights.sbomify.com/CVE-2017-1000099/"}