|
VCID-3h9c-dfvd-g3a4
|
Time-of-check Time-of-use (TOCTOU) Race Condition
libcurl can be told to save cookie, HSTS and/or alt-svc data to files. When
doing this, it called `stat()` followed by `fopen()` in a way that made it
vulnerable to a TOCTOU race condition problem.
By exploiting this flaw, an attacker could trick the victim to create or
overwrite protected files holding this data in ways it was not intended to.
|
CVE-2023-32001
|
|
VCID-47qb-2qkw-1qej
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-28321
|
|
VCID-4e1k-7bj9-hfch
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-23914
|
|
VCID-4gze-cwtp-2bgr
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-23915
|
|
VCID-7srk-hshe-h3f4
|
Improper Authentication
An authentication bypass vulnerability exists in libcurl 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-9ggp-5wfj-ufcq
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2022-43552
|
|
VCID-arjz-67yz-wkg9
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-27533
|
|
VCID-bz4u-6rft-s3a8
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-38039
|
|
VCID-cbah-e86c-w3fj
|
Improper Authentication
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-ddgz-rczw-jqfw
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-28320
|
|
VCID-gnx2-djyk-uyaf
|
Cookie injection with none file
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 does 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.
|
CVE-2023-38546
|
|
VCID-ke81-x2ze-rbc5
|
Double Free
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
|
|
VCID-m15r-v9sr-2bbn
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-28319
|
|
VCID-ms2r-94ph-yyh3
|
Improper Authentication
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-n57n-cymy-z7dr
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-23916
|
|
VCID-s73y-y7v7-43cm
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-28322
|
|
VCID-syz5-5y6f-s7er
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2023-27534
|
|
VCID-tcqe-7skm-b3fz
|
Out-of-bounds Write
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.
|
CVE-2023-38545
|
|
VCID-xpss-yndr-mycj
|
Multiple vulnerabilities have been discovered in curl, the worst of which could result in arbitrary code execution.
|
CVE-2022-43551
|