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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2017-10-04T01:00:00
Updated: 2024-08-05T21:53:06.676Z
Reserved: 2017-10-03T00:00:00
Link: CVE-2017-1000099
Vulnrichment
No data.
NVD
Status : Modified
Published: 2017-10-05T01:29:04.023
Modified: 2024-11-21T03:04:09.487
Link: CVE-2017-1000099
Redhat