CoreCVE
Back

MEDIUM

curl: TFTP sends more than buffer size

Published Oct 4, 2017

Description

When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The endto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. Limit curl's redirect protocols with --proto-redir and libcurl's with CURLOPT_REDIR_PROTOCOLS.

Affected products

Remediation

Red Hat statement

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Metrics

Weaknesses (2)

CWE-125

Out-of-bounds Read

CWE-200

Exposure of Sensitive Information

References (11)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner mitre
Published Oct 4, 2017
Updated Apr 16, 2026
Reserved Oct 3, 2017
Link CVE-2017-1000100
CISA Vulnrichment
Updated Apr 16, 2026
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2017-1000100
Red Hat
Severity Low
Public date Aug 9, 2017
Links CVE-2017-1000100 - Bugzilla