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.
References
Link Resource
http://www.securityfocus.com/bid/100281 VDB Entry Third Party Advisory
http://www.securitytracker.com/id/1039119 Third Party Advisory VDB Entry
https://curl.haxx.se/0809C.patch Patch Vendor Advisory
https://curl.haxx.se/docs/adv_20170809C.html Vendor Advisory
https://security.gentoo.org/glsa/201709-14 Patch Third Party Advisory VDB Entry
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: mitre

Published: 2017-10-04T01:00:00

Updated: 2017-10-04T09:57:01

Reserved: 2017-10-03T00:00:00


Link: CVE-2017-1000099

JSON object: View

cve-icon NVD Information

Status : Analyzed

Published: 2017-10-05T01:29:04.023

Modified: 2017-11-01T19:23:23.233


Link: CVE-2017-1000099

JSON object: View

cve-icon Redhat Information

No data.

CWE