Search for packages
| purl | pkg:generic/curl.se/curl@8.0.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1ard-hhvx-aaab
Aliases: CVE-2024-2004 |
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 present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug. |
Affected by 8 other vulnerabilities. |
|
VCID-1dvu-a5gy-aaah
Aliases: CVE-2024-7264 |
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 to a crash, but can also lead to heap contents getting returned to the application when [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used. |
Affected by 7 other vulnerabilities. |
|
VCID-7j8d-dux3-aaaa
Aliases: CVE-2023-28320 |
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()` and `siglongjmp()`. When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave. |
Affected by 13 other vulnerabilities. |
|
VCID-97mb-c19v-bqcx
Aliases: CVE-2025-0725 |
libcurl: Buffer Overflow in libcurl via zlib Integer Overflow |
Affected by 2 other vulnerabilities. |
|
VCID-gvnm-3697-aaap
Aliases: CVE-2024-2398 |
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 therefore not easily detected by an application. |
Affected by 8 other vulnerabilities. |
|
VCID-gw9j-gggs-t7at
Aliases: CVE-2024-11053 |
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 password. |
Affected by 5 other vulnerabilities. |
|
VCID-gwcj-g9n8-aaas
Aliases: CVE-2023-38546 |
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 provides a function call that duplicates en easy handle called [curl_easy_duphandle](https://curl.se/libcurl/c/curl_easy_duphandle.html). If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as `none` (using the four ASCII letters, no quotes). Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named `none` - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course. |
Affected by 10 other vulnerabilities. |
|
VCID-jxju-r4ej-ffev
Aliases: CVE-2024-9681 |
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 a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended. |
Affected by 5 other vulnerabilities. |
|
VCID-ky1x-6r1w-aaae
Aliases: CVE-2023-28319 |
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 might be shown to users or otherwise get leaked and revealed. |
Affected by 13 other vulnerabilities. |
|
VCID-kz7x-9spe-aaar
Aliases: CVE-2023-38545 |
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 instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with. |
Affected by 10 other vulnerabilities. |
|
VCID-pjd5-rdfe-aaak
Aliases: CVE-2023-46218 |
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 against the Public Suffix List (PSL). For example a cookie could be set with `domain=co.UK` when the URL used a lower case hostname `curl.co.uk`, even though `co.uk` is listed as a PSL domain. |
Affected by 11 other vulnerabilities. |
|
VCID-t6fs-2jn9-bfbg
Aliases: CVE-2025-0167 |
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 login and password. A rare circumstance. |
Affected by 2 other vulnerabilities. |
|
VCID-uegp-s96r-aaaj
Aliases: CVE-2023-38039 |
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. |
Affected by 12 other vulnerabilities. |
|
VCID-uvwv-wpr9-aaas
Aliases: CVE-2023-28321 |
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 provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to pattern match, but the wildcard check in curl could still check for `x*`, which would match even though the IDN name most likely contained nothing even resembling an `x`. |
Affected by 13 other vulnerabilities. |
|
VCID-w4x7-57vc-7yh7
Aliases: CVE-2024-8096 |
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 certficate. |
Affected by 6 other vulnerabilities. |
|
VCID-w8yq-q8v2-aaaa
Aliases: CVE-2023-28322 |
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 wasused to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST. |
Affected by 13 other vulnerabilities. |
|
VCID-x591-qs6b-aaar
Aliases: CVE-2023-46219 |
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 by 11 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-84jx-d3z4-aaag | 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 could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system. |
CVE-2023-27533
|
| VCID-eutp-u3c4-aaae | An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed. |
CVE-2023-27536
|
| VCID-jd3p-qdc8-aaah | 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 crafting a path like /~2/foo while accessing a server with a specific user. |
CVE-2023-27534
|
| VCID-pzhv-dhbt-aaan | An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection. |
CVE-2023-27538
|
| VCID-rhpa-297r-aaam | An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information. |
CVE-2023-27535
|
| VCID-w4hj-fw9e-aaaa | A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free. |
CVE-2023-27537
|
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-03-28T13:43:16.561930+00:00 | Curl Importer | Affected by | VCID-t6fs-2jn9-bfbg | https://curl.se/docs/CVE-2025-0167.json | 36.0.0 |
| 2025-03-28T13:43:16.273067+00:00 | Curl Importer | Affected by | VCID-97mb-c19v-bqcx | https://curl.se/docs/CVE-2025-0725.json | 36.0.0 |
| 2025-01-16T20:10:06.401745+00:00 | Curl Importer | Affected by | VCID-gw9j-gggs-t7at | https://curl.se/docs/CVE-2024-11053.json | 35.1.0 |
| 2024-12-11T08:35:47.938162+00:00 | Curl Importer | Affected by | VCID-gw9j-gggs-t7at | https://curl.se/docs/CVE-2024-11053.json | 35.0.0 |
| 2024-11-19T00:55:33.607277+00:00 | Curl Importer | Affected by | VCID-jxju-r4ej-ffev | https://curl.se/docs/CVE-2024-9681.json | 34.3.2 |
| 2024-09-18T09:28:47.555853+00:00 | Curl Importer | Fixing | VCID-84jx-d3z4-aaag | https://curl.se/docs/CVE-2023-27533.json | 34.0.1 |
| 2024-09-18T09:28:46.637785+00:00 | Curl Importer | Fixing | VCID-jd3p-qdc8-aaah | https://curl.se/docs/CVE-2023-27534.json | 34.0.1 |
| 2024-09-18T09:28:45.983823+00:00 | Curl Importer | Fixing | VCID-rhpa-297r-aaam | https://curl.se/docs/CVE-2023-27535.json | 34.0.1 |
| 2024-09-18T09:28:45.233362+00:00 | Curl Importer | Fixing | VCID-eutp-u3c4-aaae | https://curl.se/docs/CVE-2023-27536.json | 34.0.1 |
| 2024-09-18T09:28:44.705587+00:00 | Curl Importer | Fixing | VCID-w4hj-fw9e-aaaa | https://curl.se/docs/CVE-2023-27537.json | 34.0.1 |
| 2024-09-18T09:28:44.666626+00:00 | Curl Importer | Fixing | VCID-pzhv-dhbt-aaan | https://curl.se/docs/CVE-2023-27538.json | 34.0.1 |
| 2024-09-18T09:28:43.970078+00:00 | Curl Importer | Affected by | VCID-ky1x-6r1w-aaae | https://curl.se/docs/CVE-2023-28319.json | 34.0.1 |
| 2024-09-18T09:28:43.866805+00:00 | Curl Importer | Affected by | VCID-7j8d-dux3-aaaa | https://curl.se/docs/CVE-2023-28320.json | 34.0.1 |
| 2024-09-18T09:28:42.992870+00:00 | Curl Importer | Affected by | VCID-uvwv-wpr9-aaas | https://curl.se/docs/CVE-2023-28321.json | 34.0.1 |
| 2024-09-18T09:28:42.195780+00:00 | Curl Importer | Affected by | VCID-w8yq-q8v2-aaaa | https://curl.se/docs/CVE-2023-28322.json | 34.0.1 |
| 2024-09-18T09:28:41.271504+00:00 | Curl Importer | Affected by | VCID-uegp-s96r-aaaj | https://curl.se/docs/CVE-2023-38039.json | 34.0.1 |
| 2024-09-18T09:28:41.172983+00:00 | Curl Importer | Affected by | VCID-kz7x-9spe-aaar | https://curl.se/docs/CVE-2023-38545.json | 34.0.1 |
| 2024-09-18T09:28:40.966908+00:00 | Curl Importer | Affected by | VCID-gwcj-g9n8-aaas | https://curl.se/docs/CVE-2023-38546.json | 34.0.1 |
| 2024-09-18T09:28:39.959772+00:00 | Curl Importer | Affected by | VCID-pjd5-rdfe-aaak | https://curl.se/docs/CVE-2023-46218.json | 34.0.1 |
| 2024-09-18T09:28:39.541158+00:00 | Curl Importer | Affected by | VCID-x591-qs6b-aaar | https://curl.se/docs/CVE-2023-46219.json | 34.0.1 |
| 2024-09-18T09:28:39.403457+00:00 | Curl Importer | Affected by | VCID-1ard-hhvx-aaab | https://curl.se/docs/CVE-2024-2004.json | 34.0.1 |
| 2024-09-18T09:28:39.251649+00:00 | Curl Importer | Affected by | VCID-gvnm-3697-aaap | https://curl.se/docs/CVE-2024-2398.json | 34.0.1 |
| 2024-09-18T09:28:38.673924+00:00 | Curl Importer | Affected by | VCID-1dvu-a5gy-aaah | https://curl.se/docs/CVE-2024-7264.json | 34.0.1 |
| 2024-09-18T09:28:38.087670+00:00 | Curl Importer | Affected by | VCID-w4x7-57vc-7yh7 | https://curl.se/docs/CVE-2024-8096.json | 34.0.1 |