rpm package
suse/curl&distro=SUSE Linux Enterprise Module for Basesystem 15 SP6
pkg:rpm/suse/curl&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP6
Vulnerabilities (15)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-11563 | — | < 8.14.1-150600.4.31.1 | 8.14.1-150600.4.31.1 | Feb 25, 2026 | URLs containing percent-encoded slashes (`/` or `\`) can trick wcurl into saving the output file outside of the current directory without the user explicitly asking for it. This flaw only affects the wcurl command line tool. | ||
| CVE-2025-9086 | Hig | 7.5 | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Sep 12, 2025 | 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path | |
| CVE-2025-10148 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Sep 12, 2025 | curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traf | ||
| CVE-2025-5399 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Jun 7, 2025 | Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop. There is no other way for the application to escape or exit this loop other than killing the thread/process. This mig | ||
| CVE-2025-5025 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | May 28, 2025 | libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it | ||
| CVE-2025-4947 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | May 28, 2025 | libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks. | ||
| CVE-2025-0725 | — | < 8.6.0-150600.4.21.1 | 8.6.0-150600.4.21.1 | Feb 5, 2025 | When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. | ||
| CVE-2025-0665 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Feb 5, 2025 | libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve. | ||
| CVE-2025-0167 | — | < 8.6.0-150600.4.21.1 | 8.6.0-150600.4.21.1 | Feb 5, 2025 | When asked to 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 a `default` entry that omits both l | ||
| CVE-2024-11053 | — | < 8.6.0-150600.4.15.1 | 8.6.0-150600.4.15.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.6.0-150600.4.12.1 | 8.6.0-150600.4.12.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.6.0-150600.4.6.1 | 8.6.0-150600.4.6.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.6.0-150600.4.3.1 | 8.6.0-150600.4.3.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-6874 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Jul 24, 2024 | 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 ba | ||
| CVE-2024-6197 | — | < 8.6.0-150600.4.3.1 | 8.6.0-150600.4.3.1 | Jul 24, 2024 | 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 |
- CVE-2025-11563Feb 25, 2026affected < 8.14.1-150600.4.31.1fixed 8.14.1-150600.4.31.1
URLs containing percent-encoded slashes (`/` or `\`) can trick wcurl into saving the output file outside of the current directory without the user explicitly asking for it. This flaw only affects the wcurl command line tool.
- affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path
- CVE-2025-10148Sep 12, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traf
- CVE-2025-5399Jun 7, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop. There is no other way for the application to escape or exit this loop other than killing the thread/process. This mig
- CVE-2025-5025May 28, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it
- CVE-2025-4947May 28, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.
- CVE-2025-0725Feb 5, 2025affected < 8.6.0-150600.4.21.1fixed 8.6.0-150600.4.21.1
When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow.
- CVE-2025-0665Feb 5, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.
- CVE-2025-0167Feb 5, 2025affected < 8.6.0-150600.4.21.1fixed 8.6.0-150600.4.21.1
When asked to 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 a `default` entry that omits both l
- CVE-2024-11053Dec 11, 2024affected < 8.6.0-150600.4.15.1fixed 8.6.0-150600.4.15.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.6.0-150600.4.12.1fixed 8.6.0-150600.4.12.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.6.0-150600.4.6.1fixed 8.6.0-150600.4.6.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.6.0-150600.4.3.1fixed 8.6.0-150600.4.3.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-6874Jul 24, 2024affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
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 ba
- CVE-2024-6197Jul 24, 2024affected < 8.6.0-150600.4.3.1fixed 8.6.0-150600.4.3.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