| Package | Affected versions | Patched versions |
|---|---|---|
| libcurl | = 7.15.0= 7.15.1= 7.15.2= 7.15.3= 7.15.4= 7.15.5= 7.16.0= 7.16.1= 7.16.2= 7.16.3= 7.16.4= 7.17.0= 7.17.1= 7.18.0= 7.18.1= 7.18.2= 7.19.0= 7.19.1= 7.19.2= 7.19.3= 7.19.4= 7.19.5= 7.19.6= 7.19.7= 7.20.0= 7.20.1= 7.21.0= 7.21.1= 7.21.2= 7.21.3= 7.21.4= 7.21.5= 7.21.6= 7.21.7= 7.22.0= 7.23.0= 7.23.1= 7.24.0= 7.25.0= 7.26.0= 7.27.0= 7.28.0= 7.28.1= 7.29.0= 7.30.0= 7.31.0= 7.32.0= 7.33.0= 7.34.0= 7.35.0= 7.36.0= 7.37.0= 7.37.1= 7.38.0= 7.39= 7.40.0= 7.41.0= 7.42.0= 7.42.1= 7.43.0= 7.44.0= 7.45.0= 7.46.0= 7.47.0= 7.47.1= 7.48.0= 7.49.0= 7.49.1= 7.50.0= 7.50.1= 7.50.2= 7.50.3= 7.51.0= 7.52.0= 7.52.1= 7.53.0= 7.53.1= 7.54.0= 7.54.1 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free