{"api_version":"1","generated_at":"2026-07-23T05:30:54+00:00","cve":"CVE-2017-9502","urls":{"html":"https://cve.report/CVE-2017-9502","api":"https://cve.report/api/cve/CVE-2017-9502.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2017-9502","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-9502"},"summary":{"title":"CVE-2017-9502","description":"In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allows an application to set which protocol libcurl should attempt to use when given a URL without a scheme part, had a flaw that could lead to it overwriting a heap based memory buffer with seven bytes. If the default protocol is specified to be FILE or a file: URL lacks two slashes, the given \"URL\" starts with a drive letter, and libcurl is built for Windows or DOS, then libcurl would copy the path 7 bytes off, so that the end of the given path would write beyond the malloc buffer (7 bytes being the length in bytes of the ascii string \"file://\").","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2017-06-14 13:29:00","updated_at":"2017-07-08 01:29:00"},"problem_types":["CWE-119"],"metrics":[],"references":[{"url":"http://openwall.com/lists/oss-security/2017/06/14/1","name":"http://openwall.com/lists/oss-security/2017/06/14/1","refsource":"CONFIRM","tags":["Mailing List","Third Party Advisory"],"title":"oss-security - [SECURITY ADVISORY] curl: URL file scheme drive letter buffer\n overflow","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://www.securityfocus.com/bid/99120","name":"99120","refsource":"BID","tags":["Third Party Advisory","VDB Entry"],"title":"cURL/libcURL 'b/lib/url.c' Heap Based Buffer Overflow Vulnerability","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"http://www.securitytracker.com/id/1038697","name":"1038697","refsource":"SECTRACK","tags":[],"title":"libcurl 'file' Protocol Buffer Overflow Lets Local Users Execute Arbitrary Code - SecurityTracker","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://curl.haxx.se/docs/adv_20170614.html","name":"https://curl.haxx.se/docs/adv_20170614.html","refsource":"CONFIRM","tags":["Vendor Advisory"],"title":"curl - default protocol drive letter buffer overflow","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-9502","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-9502","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2017","cve_id":"9502","vulnerable":"1","versionEndIncluding":"7.54.0","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"haxx","cpe5":"curl","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2017-9502","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allows an application to set which protocol libcurl should attempt to use when given a URL without a scheme part, had a flaw that could lead to it overwriting a heap based memory buffer with seven bytes. If the default protocol is specified to be FILE or a file: URL lacks two slashes, the given \"URL\" starts with a drive letter, and libcurl is built for Windows or DOS, then libcurl would copy the path 7 bytes off, so that the end of the given path would write beyond the malloc buffer (7 bytes being the length in bytes of the ascii string \"file://\")."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"1038697","refsource":"SECTRACK","url":"http://www.securitytracker.com/id/1038697"},{"name":"http://openwall.com/lists/oss-security/2017/06/14/1","refsource":"CONFIRM","url":"http://openwall.com/lists/oss-security/2017/06/14/1"},{"name":"https://curl.haxx.se/docs/adv_20170614.html","refsource":"CONFIRM","url":"https://curl.haxx.se/docs/adv_20170614.html"},{"name":"99120","refsource":"BID","url":"http://www.securityfocus.com/bid/99120"}]}},"nvd":{"publishedDate":"2017-06-14 13:29:00","lastModifiedDate":"2017-07-08 01:29:00","problem_types":["CWE-119"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"LOW","baseScore":5.3,"baseSeverity":"MEDIUM"},"exploitabilityScore":3.9,"impactScore":1.4},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:N/I:N/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"PARTIAL","baseScore":5},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*","versionEndIncluding":"7.54.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2017","CveId":"9502","Ordinal":"106519","Title":"CVE-2017-9502","CVE":"CVE-2017-9502","Year":"2017"},"notes":[{"CveYear":"2017","CveId":"9502","Ordinal":"1","NoteData":"In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allows an application to set which protocol libcurl should attempt to use when given a URL without a scheme part, had a flaw that could lead to it overwriting a heap based memory buffer with seven bytes. If the default protocol is specified to be FILE or a file: URL lacks two slashes, the given \"URL\" starts with a drive letter, and libcurl is built for Windows or DOS, then libcurl would copy the path 7 bytes off, so that the end of the given path would write beyond the malloc buffer (7 bytes being the length in bytes of the ascii string \"file://\").","Type":"Description","Title":null},{"CveYear":"2017","CveId":"9502","Ordinal":"2","NoteData":"2017-06-14","Type":"Other","Title":"Published"},{"CveYear":"2017","CveId":"9502","Ordinal":"3","NoteData":"2017-07-07","Type":"Other","Title":"Modified"}]}}}