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 MITRE CVE dictionary describes this issue as:
Find out more about CVE-2017-1000099 from the MITRE CVE dictionary dictionary and NIST NVD.
NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.
| CVSS3 Base Score | 4.7 |
|---|---|
| CVSS3 Base Metrics | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| Attack Vector | Local |
| Attack Complexity | High |
| Privileges Required | Low |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity Impact | None |
| Availability Impact | None |
| Platform | Package | State |
|---|---|---|
| Red Hat Software Collections for Red Hat Enterprise Linux | httpd24-curl | Not affected |
| Red Hat JBoss Web Server 3.0 | curl | Not affected |
| Red Hat Enterprise Linux 7 | curl | Not affected |
| Red Hat Enterprise Linux 6 | curl | Not affected |
| Red Hat Enterprise Linux 5 | curl | Not affected |
| Red Hat Ceph Storage 2 | curl | Not affected |
| RHEV Manager 3 | mingw-virt-viewer | Not affected |
| .NET Core 2.0 on Red Hat Enterprise Linux | rh-dotnet20-curl | Not affected |
| .NET Core 1.0 on Red Hat Enterprise Linux | rh-dotnetcore10-curl | Not affected |
| .NET Core 1.0 on Red Hat Enterprise Linux | rh-dotnetcore11-curl | Not affected |
Vulmon