CVE-2017-1000099: Infoleak
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.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2017-1000099?
CVE-2017-1000099 is classified as a medium severity vulnerability due to potential exposure of sensitive data.
How do I fix CVE-2017-1000099?
To mitigate CVE-2017-1000099, upgrade libcurl to version 7.54.2 or later, which addresses the issue.
What versions of libcurl are affected by CVE-2017-1000099?
CVE-2017-1000099 affects libcurl version 7.54.1 specifically.
What type of data exposure is associated with CVE-2017-1000099?
CVE-2017-1000099 can lead to unintended exposure of private data from the application’s heap.
Is CVE-2017-1000099 a remote code execution vulnerability?
No, CVE-2017-1000099 is not a remote code execution vulnerability; it primarily affects data privacy.