Homepage

Information Exposure Affecting curl-debuginfo package, versions <0:7.51.0-9.75.amzn1

Severity

 Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.41% (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-AMZN201803-CURLDEBUGINFO-1707702
  • published27 Sept 2021
  • disclosed5 Oct 2017
Report a new vulnerability Found a mistake?

Introduced: 5 Oct 2017

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

How to fix?

Upgrade Amazon-Linux:2018.03 curl-debuginfo to version 0:7.51.0-9.75.amzn1 or higher.
This issue was patched in ALAS-2017-889.

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl-debuginfo package and not the curl-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 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.