Debian Curl vulnerabilities

CVE-2024-2398 [HIGH] CVE-2024-2398: curl - When an application tells libcurl it wants to allow HTTP/2 server push, and the ... 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 headers and instead leaks the memory. Further, this error condition fails silently and is therefo

CVE-2024-9681 [MEDIUM] CVE-2024-9681: curl - When curl is asked to use HSTS, the expiry time for a subdomain might overwrite ... 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 transfers with hosts like `x.example.com` as well as `example.com` where the first host is

CVE-2024-8096 [MEDIUM] CVE-2024-8096: curl - When curl is told to use the Certificate Status Request TLS extension, often ref... 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 another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad c

CVE-2024-7264 [MEDIUM] CVE-2024-7264: curl - libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an A... 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 to a heap buffer area that is not (purposely) null terminated. This flaw most likely leads t

CVE-2024-11053 [LOW] CVE-2024-11053: curl - When asked to both use a `.netrc` file for credentials and to follow HTTP redire... 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 target hostname but the entry either omits just the password or omits both login and passwor

CVE-2024-2379 [MEDIUM] CVE-2024-2379: curl - libcurl skips the certificate verification for a QUIC connection under certain c... libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.7.1-1) sid: resolved (fixed

CVE-2024-2466 [MEDIUM] CVE-2024-2466: curl - libcurl did not check the server certificate of TLS connections done to a host s... libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, S

CVE-2024-2004 [LOW] CVE-2024-2004: curl - When a protocol selection parameter option disables all protocols without adding... 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 protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only

CVE-2024-0853 [MEDIUM] CVE-2024-0853: curl - curl inadvertently kept the SSL session ID for connections in its cache even whe... curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (*OCSP stapling*) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 8.6.0-1) sid: re

CVE-2024-6874 [MEDIUM] CVE-2024-6874: curl - libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_g... libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading outside of a stack based buffer when built to use the *macidn* IDN backend. The conversion function then fills up the provided buffer exactly - but does not nul

CVE-2024-6197 [HIGH] CVE-2024-6197: curl - libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 ... libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect an invalid field and return error. Unfortunately, when doing so it also invokes `free()` on a 4 byte localstack buffer. Most modern malloc implementations detect this error and immediately abort. Some however accept the input pointer and add that memory to its list

CVE-2023-38545 [CRITICAL] CVE-2023-38545: curl - This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.... 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 bytes. If the host name is detected to be longer, curl switches to local name resolving and

CVE-2023-23914 [CRITICAL] CVE-2023-23914: curl - A cleartext transmission of sensitive information vulnerability exists in curl <... A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly b

CVE-2023-27533 [HIGH] CVE-2023-27533: curl - A vulnerability in input validation exists in curl <8.0 during communication usi... A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability coul

CVE-2023-38039 [HIGH] CVE-2023-38039: curl - When curl retrieves an HTTP response, it stores the incoming headers so that the... 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 endless series of headers and eventually cause curl to run out of heap memory. Scope: local bookwo

CVE-2023-28319 [HIGH] CVE-2023-28319: curl - A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers ... 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 freed) hash. This flaw risks inserting sensitive heap-based data into the error message that m

CVE-2023-27534 [HIGH] CVE-2023-27534: curl - A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes ... A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by cra

CVE-2023-23916 [MEDIUM] CVE-2023-23916: curl - An allocation of resources without limits or throttling vulnerability exists in ... An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header

CVE-2023-46218 [MEDIUM] CVE-2023-46218: curl - This flaw allows a malicious HTTP server to set "super cookies" in curl that are... 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 by exploiting a mixed case flaw in curl's function that verifies a given cookie domain ag

CVE-2023-23915 [MEDIUM] CVE-2023-23915: curl - A cleartext transmission of sensitive information vulnerability exists in curl <... A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would ho