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.
Advisories
Source ID Title
EUVD EUVD EUVD-2017-1403 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.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T21:53:06.676Z

Reserved: 2017-10-03T00:00:00

Link: CVE-2017-1000099

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-10-05T01:29:04.023

Modified: 2025-04-20T01:37:25.860

Link: CVE-2017-1000099

cve-icon Redhat

Severity : Moderate

Publid Date: 2017-08-09T00:00:00Z

Links: CVE-2017-1000099 - Bugzilla

cve-icon OpenCVE Enrichment

No data.