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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/100281 | third party advisory vdb entry |
| https://security.gentoo.org/glsa/201709-14 | patch vendor advisory third party advisory vdb entry |
| https://curl.haxx.se/0809C.patch | patch vendor advisory |
| http://www.securitytracker.com/id/1039119 | third party advisory vdb entry |
| https://curl.haxx.se/docs/adv_20170809C.html | vendor advisory |