rpm package
suse/curl-openssl1&distro=SUSE Linux Enterprise Server 11-SECURITY
pkg:rpm/suse/curl-openssl1&distro=SUSE%20Linux%20Enterprise%20Server%2011-SECURITY
Vulnerabilities (40)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2016-8616 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Aug 1, 2018 | A flaw was found in curl before version 7.51.0 When re-using a connection, curl was doing case insensitive comparisons of user name and password with the existing connections. This means that if an unused connection with proper credentials exists for a protocol that has connectio | ||
| CVE-2016-8615 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Aug 1, 2018 | A flaw was found in curl before version 7.51. If cookie state is written into a cookie jar file that is later read back and used for subsequent requests, a malicious HTTP server can inject new cookies for arbitrary domains into said cookie jar. | ||
| CVE-2016-8621 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Jul 31, 2018 | The `curl_getdate` function in curl before version 7.51.0 is vulnerable to an out of bounds read if it receives an input with one digit short. | ||
| CVE-2016-8617 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Jul 31, 2018 | The base64 encode function in curl before version 7.51.0 is prone to a buffer being under allocated in 32bit systems if it receives at least 1Gb as input via `CURLOPT_USERNAME`. | ||
| CVE-2016-8624 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Jul 31, 2018 | curl before version 7.51.0 doesn't parse the authority component of the URL correctly when the host name part ends with a '#' character, and could instead be tricked into connecting to a different host. This may have security implications if you for example use an URL parser that | ||
| CVE-2016-8622 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Jul 31, 2018 | The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus th | ||
| CVE-2016-8618 | — | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Jul 31, 2018 | The libcurl API function called `curl_maprintf()` before version 7.51.0 can be tricked into doing a double-free due to an unsafe `size_t` multiplication, on systems using 32 bit `size_t` variables. | ||
| CVE-2018-1000301 | Cri | 9.1 | < 7.37.0-70.30.1 | 7.37.0-70.30.1 | May 24, 2018 | curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability | |
| CVE-2016-9586 | — | < 7.19.7-1.69.1 | 7.19.7-1.69.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-70.27.1 | 7.37.0-70.27.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-70.27.1 | 7.37.0-70.27.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-70.27.1 | 7.37.0-70.27.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.19.7-1.70.13.1 | 7.19.7-1.70.13.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-1000254 | Hig | 7.5 | < 7.19.7-1.70.8.1 | 7.19.7-1.70.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-1000100 | Med | 6.5 | < 7.19.7-1.70.3.1 | 7.19.7-1.70.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.19.7-1.69.1 | 7.19.7-1.69.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-7167 | Cri | 9.8 | < 7.19.7-1.64.1 | 7.19.7-1.64.1 | Oct 7, 2016 | Multiple integer overflows in the (1) curl_escape, (2) curl_easy_escape, (3) curl_unescape, and (4) curl_easy_unescape functions in libcurl before 7.50.3 allow attackers to have unspecified impact via a string of length 0xffffffff, which triggers a heap-based buffer overflow. | |
| CVE-2016-7141 | Hig | 7.5 | < 7.19.7-1.61.1 | 7.19.7-1.61.1 | Oct 3, 2016 | curl and libcurl before 7.50.2, when built with NSS and the libnsspem.so library is available at runtime, allow remote attackers to hijack the authentication of a TLS connection by leveraging reuse of a previously loaded client certificate from file for a connection for which no | |
| CVE-2016-5420 | Hig | 7.5 | < 7.19.7-1.61.1 | 7.19.7-1.61.1 | Aug 10, 2016 | curl and libcurl before 7.50.1 do not check the client certificate when choosing the TLS connection to reuse, which might allow remote attackers to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate. | |
| CVE-2016-5419 | Hig | 7.5 | < 7.19.7-1.61.1 | 7.19.7-1.61.1 | Aug 10, 2016 | curl and libcurl before 7.50.1 do not prevent TLS session resumption when the client certificate has changed, which allows remote attackers to bypass intended restrictions by resuming a session. |
- CVE-2016-8616Aug 1, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
A flaw was found in curl before version 7.51.0 When re-using a connection, curl was doing case insensitive comparisons of user name and password with the existing connections. This means that if an unused connection with proper credentials exists for a protocol that has connectio
- CVE-2016-8615Aug 1, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
A flaw was found in curl before version 7.51. If cookie state is written into a cookie jar file that is later read back and used for subsequent requests, a malicious HTTP server can inject new cookies for arbitrary domains into said cookie jar.
- CVE-2016-8621Jul 31, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
The `curl_getdate` function in curl before version 7.51.0 is vulnerable to an out of bounds read if it receives an input with one digit short.
- CVE-2016-8617Jul 31, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
The base64 encode function in curl before version 7.51.0 is prone to a buffer being under allocated in 32bit systems if it receives at least 1Gb as input via `CURLOPT_USERNAME`.
- CVE-2016-8624Jul 31, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
curl before version 7.51.0 doesn't parse the authority component of the URL correctly when the host name part ends with a '#' character, and could instead be tricked into connecting to a different host. This may have security implications if you for example use an URL parser that
- CVE-2016-8622Jul 31, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus th
- CVE-2016-8618Jul 31, 2018affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
The libcurl API function called `curl_maprintf()` before version 7.51.0 can be tricked into doing a double-free due to an unsafe `size_t` multiplication, on systems using 32 bit `size_t` variables.
- affected < 7.37.0-70.30.1fixed 7.37.0-70.30.1
curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability
- CVE-2016-9586Apr 23, 2018affected < 7.19.7-1.69.1fixed 7.19.7-1.69.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-70.27.1fixed 7.37.0-70.27.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-70.27.1fixed 7.37.0-70.27.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-70.27.1fixed 7.37.0-70.27.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.19.7-1.70.13.1fixed 7.19.7-1.70.13.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.19.7-1.70.8.1fixed 7.19.7-1.70.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.19.7-1.70.3.1fixed 7.19.7-1.70.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.19.7-1.69.1fixed 7.19.7-1.69.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,
- affected < 7.19.7-1.64.1fixed 7.19.7-1.64.1
Multiple integer overflows in the (1) curl_escape, (2) curl_easy_escape, (3) curl_unescape, and (4) curl_easy_unescape functions in libcurl before 7.50.3 allow attackers to have unspecified impact via a string of length 0xffffffff, which triggers a heap-based buffer overflow.
- affected < 7.19.7-1.61.1fixed 7.19.7-1.61.1
curl and libcurl before 7.50.2, when built with NSS and the libnsspem.so library is available at runtime, allow remote attackers to hijack the authentication of a TLS connection by leveraging reuse of a previously loaded client certificate from file for a connection for which no
- affected < 7.19.7-1.61.1fixed 7.19.7-1.61.1
curl and libcurl before 7.50.1 do not check the client certificate when choosing the TLS connection to reuse, which might allow remote attackers to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate.
- affected < 7.19.7-1.61.1fixed 7.19.7-1.61.1
curl and libcurl before 7.50.1 do not prevent TLS session resumption when the client certificate has changed, which allows remote attackers to bypass intended restrictions by resuming a session.
Page 2 of 2