Page 2 of 33 results (0.004 seconds)

CVSS: 3.7EPSS: 0%CPEs: 16EXPL: 1

26 May 2023 — An information disclosure vulnerability exists in curl

CVSS: 9.1EPSS: 0%CPEs: 14EXPL: 1

26 May 2023 — A use after free vulnerability exists in curl

CVSS: 9.0EPSS: 0%CPEs: 15EXPL: 1

21 Mar 2023 — 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. Harry Sintonen discovered that curl incorrectly handled certain TELN... • https://hackerone.com/reports/1892351 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 10.0EPSS: 0%CPEs: 15EXPL: 1

21 Mar 2023 — 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. Harry Sintonen discov... • https://hackerone.com/reports/1891474 • CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') CWE-75: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) •

CVSS: 9.4EPSS: 0%CPEs: 14EXPL: 1

15 Feb 2023 — A cleartext transmission of sensitive information vulnerability exists in curl

CVSS: 6.5EPSS: 0%CPEs: 14EXPL: 0

15 Feb 2023 — A cleartext transmission of sensitive information vulnerability exists in curl

CVSS: 7.8EPSS: 0%CPEs: 16EXPL: 1

15 Feb 2023 — An allocation of resources without limits or throttling vulnerability exists in curl

CVSS: 7.8EPSS: 0%CPEs: 10EXPL: 1

21 Dec 2022 — A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. 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. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the comm... • https://hackerone.com/reports/1755083 • CWE-319: Cleartext Transmission of Sensitive Information •

CVSS: 5.9EPSS: 0%CPEs: 5EXPL: 1

21 Dec 2022 — A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path. A vulnerability was found in curl. • http://seclists.org/fulldisclosure/2023/Mar/17 • CWE-416: Use After Free •

CVSS: 8.1EPSS: 0%CPEs: 18EXPL: 0

27 Oct 2022 — curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger ... • http://seclists.org/fulldisclosure/2023/Jan/19 • CWE-415: Double Free •