Homepage

Out-of-bounds Read Affecting libcurl package, versions *

Severity

 Recommended
low

Based on CentOS security rating.

Threat Intelligence

EPSS
0.38% (74th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS7-LIBCURL-1970361
  • published26 Jul 2021
  • disclosed9 Aug 2017
Report a new vulnerability Found a mistake?

Introduced: 9 Aug 2017

CVE-2017-1000100  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

There is no fixed version for Centos:7 libcurl.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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.