rpm package
opensuse/curl&distro=openSUSE Leap 15.5
pkg:rpm/opensuse/curl&distro=openSUSE%20Leap%2015.5
Vulnerabilities (15)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-11053 | — | < 8.0.1-150400.5.59.1 | 8.0.1-150400.5.59.1 | Dec 11, 2024 | When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redirect | ||
| CVE-2024-9681 | — | < 8.0.1-150400.5.56.1 | 8.0.1-150400.5.56.1 | Nov 6, 2024 | When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform | ||
| CVE-2024-8096 | — | < 8.0.1-150400.5.50.1 | 8.0.1-150400.5.50.1 | Sep 11, 2024 | When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports | ||
| CVE-2024-7264 | — | < 8.0.1-150400.5.47.1 | 8.0.1-150400.5.47.1 | Jul 31, 2024 | libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer t | ||
| CVE-2024-2398 | — | < 8.0.1-150400.5.44.1 | 8.0.1-150400.5.44.1 | Mar 27, 2024 | When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head | ||
| CVE-2024-2004 | — | < 8.0.1-150400.5.44.1 | 8.0.1-150400.5.44.1 | Mar 27, 2024 | When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protoc | ||
| CVE-2023-46219 | Med | 5.3 | < 8.0.1-150400.5.36.1 | 8.0.1-150400.5.36.1 | Dec 12, 2023 | When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use. | |
| CVE-2023-46218 | Med | 6.5 | < 8.0.1-150400.5.36.1 | 8.0.1-150400.5.36.1 | Dec 7, 2023 | This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this | |
| CVE-2023-38546 | Low | 3.7 | < 8.0.1-150400.5.32.1 | 8.0.1-150400.5.32.1 | Oct 18, 2023 | This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl | |
| CVE-2023-38545 | Cri | 9.8 | < 8.0.1-150400.5.32.1 | 8.0.1-150400.5.32.1 | Oct 18, 2023 | This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 byt | |
| CVE-2023-38039 | — | < 8.0.1-150400.5.29.1 | 8.0.1-150400.5.29.1 | Sep 15, 2023 | When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endles | ||
| CVE-2023-28322 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was | ||
| CVE-2023-28321 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi | ||
| CVE-2023-28320 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()` an | ||
| CVE-2023-28319 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now fre |
- CVE-2024-11053Dec 11, 2024affected < 8.0.1-150400.5.59.1fixed 8.0.1-150400.5.59.1
When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redirect
- CVE-2024-9681Nov 6, 2024affected < 8.0.1-150400.5.56.1fixed 8.0.1-150400.5.56.1
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform
- CVE-2024-8096Sep 11, 2024affected < 8.0.1-150400.5.50.1fixed 8.0.1-150400.5.50.1
When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports
- CVE-2024-7264Jul 31, 2024affected < 8.0.1-150400.5.47.1fixed 8.0.1-150400.5.47.1
libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer t
- CVE-2024-2398Mar 27, 2024affected < 8.0.1-150400.5.44.1fixed 8.0.1-150400.5.44.1
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head
- CVE-2024-2004Mar 27, 2024affected < 8.0.1-150400.5.44.1fixed 8.0.1-150400.5.44.1
When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protoc
- affected < 8.0.1-150400.5.36.1fixed 8.0.1-150400.5.36.1
When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.
- affected < 8.0.1-150400.5.36.1fixed 8.0.1-150400.5.36.1
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this
- affected < 8.0.1-150400.5.32.1fixed 8.0.1-150400.5.32.1
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl
- affected < 8.0.1-150400.5.32.1fixed 8.0.1-150400.5.32.1
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 byt
- CVE-2023-38039Sep 15, 2023affected < 8.0.1-150400.5.29.1fixed 8.0.1-150400.5.29.1
When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endles
- CVE-2023-28322May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was
- CVE-2023-28321May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi
- CVE-2023-28320May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()` an
- CVE-2023-28319May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now fre