Summary
Detail | |||
---|---|---|---|
Vendor | Haxx | First view | 2005-05-02 |
Product | Libcurl | Last view | 2023-10-18 |
Version | Type | ||
Update | |||
Edition | |||
Language | |||
Sofware Edition | |||
Target Software | |||
Target Hardware | |||
Other |
Activity : Overall
COMMON PLATFORM ENUMERATION: Repartition per Version
Related : CVE
Date | Alert | Description | |
---|---|---|---|
3.7 | 2023-10-18 | 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. |
9.8 | 2023-10-18 | 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. |
5.5 | 2023-03-30 | CVE-2023-27538 | 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. |
5.9 | 2023-03-30 | CVE-2023-27537 | 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. |
5.9 | 2023-03-30 | CVE-2023-27536 | 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. |
5.9 | 2023-03-30 | CVE-2023-27535 | 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. |
9.1 | 2021-09-23 | CVE-2021-22945 | When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it *again*. |
3.7 | 2021-08-05 | CVE-2021-22924 | libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths *case insensitively*,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate. |
3.7 | 2021-04-01 | CVE-2021-22890 | curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check. |
5.3 | 2021-04-01 | CVE-2021-22876 | curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP requests, and therefore risks leaking sensitive data to the server that is the target of the second HTTP request. |
7.5 | 2020-12-14 | CVE-2020-8286 | curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response. |
7.5 | 2020-12-14 | CVE-2020-8285 | curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing. |
7.5 | 2020-12-14 | CVE-2020-8231 | Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data. |
7.8 | 2019-05-28 | CVE-2019-5436 | A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1. |
7.5 | 2019-02-06 | CVE-2019-3823 | libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to `smtp_endofresp()` isn't NUL terminated and contains no character ending the parsed number, and `len` is set to 5, then the `strtol()` call reads beyond the allocated buffer. The read contents will not be returned to the caller. |
9.8 | 2019-02-06 | CVE-2019-3822 | libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (`lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()`), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header. |
7.5 | 2019-02-06 | CVE-2018-16890 | libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (`lib/vauth/ntlm.c:ntlm_decode_type2_target`) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds. |
9.8 | 2018-09-05 | CVE-2018-14618 | curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.) |
9.8 | 2018-07-31 | CVE-2016-8622 | The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get either just truncated or both truncated and turned negative. That could then lead to libcurl writing outside of its heap based buffer. |
7.5 | 2018-07-16 | CVE-2017-7468 | In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range. |
9.1 | 2018-01-24 | CVE-2018-1000005 | libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something. |
9.8 | 2017-11-29 | CVE-2017-8818 | curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library. |
9.8 | 2017-11-29 | CVE-2017-8817 | The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character. |
9.8 | 2017-11-29 | CVE-2017-8816 | The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields. |
9.1 | 2017-10-31 | CVE-2017-1000257 | An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invokes strlen() on the data to figure out the length. The strlen() is called on a heap based buffer that might not be zero terminated so libcurl might read beyond the end of it into whatever memory lies after (or just crash) and then deliver that to the application as if it was actually downloaded. |
CWE : Common Weakness Enumeration
% | id | Name |
---|---|---|
12% (7) | CWE-200 | Information Exposure |
12% (7) | CWE-119 | Failure to Constrain Operations within the Bounds of a Memory Buffer |
10% (6) | CWE-287 | Improper Authentication |
9% (5) | CWE-787 | Out-of-bounds Write |
9% (5) | CWE-310 | Cryptographic Issues |
7% (4) | CWE-190 | Integer Overflow or Wraparound |
7% (4) | CWE-125 | Out-of-bounds Read |
5% (3) | CWE-20 | Improper Input Validation |
3% (2) | CWE-416 | Use After Free |
3% (2) | CWE-415 | Double Free |
3% (2) | CWE-295 | Certificate Issues |
1% (1) | CWE-706 | Use of Incorrectly-Resolved Name or Reference |
1% (1) | CWE-674 | Uncontrolled Recursion |
1% (1) | CWE-290 | Authentication Bypass by Spoofing |
1% (1) | CWE-285 | Improper Access Control (Authorization) |
1% (1) | CWE-284 | Access Control (Authorization) Issues |
1% (1) | CWE-264 | Permissions, Privileges, and Access Controls |
1% (1) | CWE-255 | Credentials Management |
1% (1) | CWE-131 | Incorrect Calculation of Buffer Size |
CAPEC : Common Attack Pattern Enumeration & Classification
id | Name |
---|---|
CAPEC-47 | Buffer Overflow via Parameter Expansion |
CAPEC-100 | Overflow Buffers |
CAPEC-123 | Buffer Attacks |
Oval Markup Language : Definitions
OvalID | Name |
---|---|
oval:org.mitre.oval:def:10273 | Multiple stack-based buffer overflows in libcURL and cURL 7.12.1, and possibl... |
oval:org.mitre.oval:def:21913 | RHSA-2011:0918: curl security update (Moderate) |
oval:org.mitre.oval:def:20630 | VMware ESXi and ESX updates to third party library and ESX Service Console |
oval:org.mitre.oval:def:13004 | DSA-2271-1 curl -- improper delegation of client credentials |
oval:org.mitre.oval:def:23218 | ELSA-2011:0918: curl security update (Moderate) |
oval:org.mitre.oval:def:18190 | USN-1721-1 -- curl vulnerability |
oval:org.mitre.oval:def:20280 | RHSA-2013:0771: curl security update (Moderate) |
oval:org.mitre.oval:def:20032 | DSA-2660-1 curl - cookie leak vulnerability |
oval:org.mitre.oval:def:18259 | USN-1801-1 -- curl vulnerability |
oval:org.mitre.oval:def:23950 | ELSA-2013:0771: curl security update (Moderate) |
oval:org.mitre.oval:def:23498 | DEPRECATED: ELSA-2013:0771: curl security update (Moderate) |
oval:org.mitre.oval:def:26023 | SUSE-SU-2013:0771-1 -- Security update for curl |
oval:org.mitre.oval:def:25795 | SUSE-SU-2013:0772-1 -- Security update for compat-curl2 |
oval:org.mitre.oval:def:25538 | SUSE-SU-2013:0773-1 -- Security update for curl, curl |
oval:org.mitre.oval:def:27357 | DEPRECATED: ELSA-2013-0771 -- curl security update (moderate) |
oval:org.mitre.oval:def:21195 | RHSA-2013:0983: curl security update (Moderate) |
oval:org.mitre.oval:def:18350 | USN-1894-1 -- curl vulnerability |
oval:org.mitre.oval:def:18308 | DSA-2713-1 curl - heap overflow |
oval:org.mitre.oval:def:23721 | ELSA-2013:0983: curl security update (Moderate) |
oval:org.mitre.oval:def:23483 | DEPRECATED: ELSA-2013:0983: curl security update (Moderate) |
oval:org.mitre.oval:def:25977 | SUSE-SU-2013:1166-1 -- Security update for compat-curl2 |
oval:org.mitre.oval:def:25912 | SUSE-SU-2013:1166-2 -- Security update for curl |
oval:org.mitre.oval:def:27292 | DEPRECATED: ELSA-2013-0983 -- curl security update (moderate) |
oval:org.mitre.oval:def:21073 | USN-2048-1 -- curl vulnerability |
oval:org.mitre.oval:def:19943 | DSA-2798-1 curl - unchecked ssl certificate host name |
Open Source Vulnerability Database (OSVDB)
id | Description |
---|---|
73686 | libcurl http_negotiate.c Curl_input_negotiate Function GSSAPI Credential Dele... |
73328 | cURL GSSAPI Client Credential Remote Disclosure |
14034 | cURL/libcURL Kerberos Authentication Multiple Function Overflows |
14033 | cURL / libcURL NTLM Authentication Curl_input_ntlm() Function Overflow |
ExploitDB Exploits
id | Description |
---|---|
24487 | cURL Buffer Overflow Vulnerability |
OpenVAS Exploits
id | Description |
---|---|
2012-07-30 | Name : CentOS Update for curl CESA-2011:0918 centos4 x86_64 File : nvt/gb_CESA-2011_0918_curl_centos4_x86_64.nasl |
2012-07-30 | Name : CentOS Update for curl CESA-2011:0918 centos5 x86_64 File : nvt/gb_CESA-2011_0918_curl_centos5_x86_64.nasl |
2012-03-15 | Name : VMSA-2012-0001 VMware ESXi and ESX updates to third party library and ESX Ser... File : nvt/gb_VMSA-2012-0001.nasl |
2012-03-12 | Name : Gentoo Security Advisory GLSA 201203-02 (cURL) File : nvt/glsa_201203_02.nasl |
2012-02-13 | Name : Fedora Update for curl FEDORA-2012-0888 File : nvt/gb_fedora_2012_0888_curl_fc15.nasl |
2012-02-06 | Name : Mac OS X Multiple Vulnerabilities (2012-001) File : nvt/gb_macosx_su12-001.nasl |
2011-08-18 | Name : CentOS Update for curl CESA-2011:0918 centos4 i386 File : nvt/gb_CESA-2011_0918_curl_centos4_i386.nasl |
2011-08-09 | Name : CentOS Update for curl CESA-2011:0918 centos5 i386 File : nvt/gb_CESA-2011_0918_curl_centos5_i386.nasl |
2011-08-03 | Name : Debian Security Advisory DSA 2271-1 (curl) File : nvt/deb_2271_1.nasl |
2011-07-27 | Name : Mandriva Update for curl MDVSA-2011:116 (curl) File : nvt/gb_mandriva_MDVSA_2011_116.nasl |
2011-07-12 | Name : Fedora Update for curl FEDORA-2011-8586 File : nvt/gb_fedora_2011_8586_curl_fc15.nasl |
2011-07-08 | Name : RedHat Update for curl RHSA-2011:0918-01 File : nvt/gb_RHSA-2011_0918-01_curl.nasl |
2011-07-08 | Name : Fedora Update for curl FEDORA-2011-8640 File : nvt/gb_fedora_2011_8640_curl_fc14.nasl |
2011-06-24 | Name : Ubuntu Update for curl USN-1158-1 File : nvt/gb_ubuntu_USN_1158_1.nasl |
2009-10-10 | Name : SLES9: Security update for curl File : nvt/sles9p5012730.nasl |
2008-09-24 | Name : Gentoo Security Advisory GLSA 200503-20 (curl) File : nvt/glsa_200503_20.nasl |
2008-09-04 | Name : FreeBSD Ports: curl File : nvt/freebsd_curl.nasl |
Information Assurance Vulnerability Management (IAVM)
id | Description |
---|---|
2015-A-0199 | Multiple Vulnerabilities in Apple Mac OS X Severity: Category I - VMSKEY: V0061337 |
2014-B-0161 | Multiple Vulnerabilities in VMware ESXi 5.1 Severity: Category I - VMSKEY: V0057717 |
2012-A-0020 | Multiple Vulnerabilities in VMware ESX 4.1 and ESXi 4.1 Severity: Category I - VMSKEY: V0031252 |
Snort® IPS/IDS
Date | Description |
---|---|
2017-04-12 | cURL and libcurl set-cookie remote code execution attempt RuleID : 41853 - Type : OS-LINUX - Revision : 4 |
2014-01-10 | libcurl MD5 digest buffer overflow attempt RuleID : 26391 - Type : PROTOCOL-POP - Revision : 3 |
Nessus® Vulnerability Scanner
id | Description |
---|---|
2019-01-08 | Name: The remote EulerOS host is missing multiple security updates. File: EulerOS_SA-2019-1002.nasl - Type: ACT_GATHER_INFO |
2019-01-03 | Name: The remote Fedora host is missing a security update. File: fedora_2018-111044d435.nasl - Type: ACT_GATHER_INFO |
2019-01-03 | Name: The remote Fedora host is missing a security update. File: fedora_2018-7f83032de6.nasl - Type: ACT_GATHER_INFO |
2018-12-28 | Name: The remote EulerOS host is missing multiple security updates. File: EulerOS_SA-2018-1427.nasl - Type: ACT_GATHER_INFO |
2018-12-20 | Name: The remote Amazon Linux 2 host is missing a security update. File: al2_ALAS-2018-1135.nasl - Type: ACT_GATHER_INFO |
2018-12-10 | Name: The remote EulerOS host is missing multiple security updates. File: EulerOS_SA-2018-1401.nasl - Type: ACT_GATHER_INFO |
2018-12-07 | Name: The remote Amazon Linux AMI host is missing a security update. File: ala_ALAS-2018-1112.nasl - Type: ACT_GATHER_INFO |
2018-11-07 | Name: The remote Debian host is missing a security update. File: debian_DLA-1568.nasl - Type: ACT_GATHER_INFO |
2018-10-26 | Name: The remote EulerOS Virtualization host is missing multiple security updates. File: EulerOS_SA-2018-1330.nasl - Type: ACT_GATHER_INFO |
2018-09-21 | Name: The remote Fedora host is missing a security update. File: fedora_2018-ba443bcb6d.nasl - Type: ACT_GATHER_INFO |
2018-09-18 | Name: The remote EulerOS Virtualization host is missing a security update. File: EulerOS_SA-2018-1237.nasl - Type: ACT_GATHER_INFO |
2018-09-10 | Name: The remote Debian host is missing a security update. File: debian_DLA-1498.nasl - Type: ACT_GATHER_INFO |
2018-09-06 | Name: The remote Slackware host is missing a security update. File: Slackware_SSA_2018-249-01.nasl - Type: ACT_GATHER_INFO |
2018-09-06 | Name: The remote Debian host is missing a security-related update. File: debian_DSA-4286.nasl - Type: ACT_GATHER_INFO |
2018-09-06 | Name: The remote FreeBSD host is missing a security-related update. File: freebsd_pkg_f4d638b9e6e54dbe8c70571dbc116174.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-0041.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-0044.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-0045.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-0048.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-0050.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2017-1_0-0095.nasl - Type: ACT_GATHER_INFO |
2018-08-17 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2018-1_0-0108.nasl - Type: ACT_GATHER_INFO |
2018-07-24 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2018-2_0-0009.nasl - Type: ACT_GATHER_INFO |
2018-07-24 | Name: The remote PhotonOS host is missing multiple security updates. File: PhotonOS_PHSA-2018-2_0-0016.nasl - Type: ACT_GATHER_INFO |
2018-04-18 | Name: The remote Amazon Linux 2 host is missing a security update. File: al2_ALAS-2018-951.nasl - Type: ACT_GATHER_INFO |