rpm package
suse/curl&distro=SUSE Linux Enterprise Desktop 12 SP2
pkg:rpm/suse/curl&distro=SUSE%20Linux%20Enterprise%20Desktop%2012%20SP2
Vulnerabilities (12)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2016-9586 | — | < 7.37.0-36.1 | 7.37.0-36.1 | Apr 23, 2018 | curl before version 7.52.0 is vulnerable to a buffer overflow when doing a large floating point output in libcurl's implementation of the printf() functions. If there are any application that accepts a format string from the outside without necessary input filtering, it could all | ||
| CVE-2018-1000122 | — | < 7.37.0-37.17.1 | 7.37.0-37.17.1 | Mar 14, 2018 | A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage | ||
| CVE-2018-1000121 | — | < 7.37.0-37.17.1 | 7.37.0-37.17.1 | Mar 14, 2018 | A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service | ||
| CVE-2018-1000120 | — | < 7.37.0-37.17.1 | 7.37.0-37.17.1 | Mar 14, 2018 | A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse. | ||
| CVE-2018-1000007 | — | < 7.37.0-37.14.1 | 7.37.0-37.14.1 | Jan 24, 2018 | libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP respon | ||
| CVE-2017-8817 | Cri | 9.8 | < 7.37.0-37.11.3 | 7.37.0-37.11.3 | Nov 29, 2017 | The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character. | |
| CVE-2017-8816 | Cri | 9.8 | < 7.37.0-37.11.3 | 7.37.0-37.11.3 | Nov 29, 2017 | The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user an | |
| CVE-2017-1000257 | Cri | 9.1 | < 7.37.0-37.8.1 | 7.37.0-37.8.1 | Oct 31, 2017 | An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function | |
| CVE-2017-1000254 | Hig | 7.5 | < 7.37.0-37.8.1 | 7.37.0-37.8.1 | Oct 6, 2017 | libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the | |
| CVE-2017-1000101 | Med | 6.5 | < 7.37.0-37.3.1 | 7.37.0-37.3.1 | Oct 5, 2017 | curl supports "globbing" of URLs, in which a user can pass a numerical range to have the tool iterate over those numbers to do a sequence of transfers. In the globbing function that parses the numerical range, there was an omission that made curl read a byte beyond the end of the | |
| CVE-2017-1000100 | Med | 6.5 | < 7.37.0-37.3.1 | 7.37.0-37.3.1 | Oct 5, 2017 | 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 | |
| CVE-2017-7407 | Low | 2.4 | < 7.37.0-36.1 | 7.37.0-36.1 | Apr 3, 2017 | The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to obtain sensitive information from process memory in opportunistic circumstances by reading a workstation screen during use of a --write-out argument ending in a '%' character, |
- CVE-2016-9586Apr 23, 2018affected < 7.37.0-36.1fixed 7.37.0-36.1
curl before version 7.52.0 is vulnerable to a buffer overflow when doing a large floating point output in libcurl's implementation of the printf() functions. If there are any application that accepts a format string from the outside without necessary input filtering, it could all
- CVE-2018-1000122Mar 14, 2018affected < 7.37.0-37.17.1fixed 7.37.0-37.17.1
A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage
- CVE-2018-1000121Mar 14, 2018affected < 7.37.0-37.17.1fixed 7.37.0-37.17.1
A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service
- CVE-2018-1000120Mar 14, 2018affected < 7.37.0-37.17.1fixed 7.37.0-37.17.1
A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.
- CVE-2018-1000007Jan 24, 2018affected < 7.37.0-37.14.1fixed 7.37.0-37.14.1
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP respon
- affected < 7.37.0-37.11.3fixed 7.37.0-37.11.3
The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.
- affected < 7.37.0-37.11.3fixed 7.37.0-37.11.3
The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user an
- affected < 7.37.0-37.8.1fixed 7.37.0-37.8.1
An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function
- affected < 7.37.0-37.8.1fixed 7.37.0-37.8.1
libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the
- affected < 7.37.0-37.3.1fixed 7.37.0-37.3.1
curl supports "globbing" of URLs, in which a user can pass a numerical range to have the tool iterate over those numbers to do a sequence of transfers. In the globbing function that parses the numerical range, there was an omission that made curl read a byte beyond the end of the
- affected < 7.37.0-37.3.1fixed 7.37.0-37.3.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
- affected < 7.37.0-36.1fixed 7.37.0-36.1
The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to obtain sensitive information from process memory in opportunistic circumstances by reading a workstation screen during use of a --write-out argument ending in a '%' character,