CVE-2017-1000099
moderate-risk
Published 2017-10-05
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.
Do I need to act?
-
0.74% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
6
CVSS 6.5/10
Medium
NETWORK
/ LOW complexity
Affected Products (1)
Affected Vendors
References (9)
Third Party Advisory
http://www.securityfocus.com/bid/100281
Third Party Advisory
http://www.securitytracker.com/id/1039119
Vendor Advisory
https://curl.haxx.se/docs/adv_20170809C.html
Third Party Advisory
http://www.securityfocus.com/bid/100281
Third Party Advisory
http://www.securitytracker.com/id/1039119
32
/ 100
moderate-risk
Severity
24/34 · High
Exploitability
3/34 · Minimal
Exposure
5/34 · Minimal