Page 2 of 108 results (0.018 seconds)

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

26 May 2023 — A denial of service vulnerability exists in curl

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

26 May 2023 — An improper certificate validation vulnerability exists in curl

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

26 May 2023 — An information disclosure vulnerability exists in curl

CVSS: 10.0EPSS: 3%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.0EPSS: 1%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: 7.8EPSS: 2%CPEs: 16EXPL: 1

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

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

06 Jan 2023 — 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: 10.0EPSS: 0%CPEs: 16EXPL: 1

27 Oct 2022 — 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 was used 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 subsequent `POST` request. The problem exists in the logic for a reused handle when it is chang... • http://seclists.org/fulldisclosure/2023/Jan/19 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-440: Expected Behavior Violation CWE-668: Exposure of Resource to Wrong Sphere •

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

02 Sep 2022 — When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings. Cuando curl es usado para recuperar y analizar las cookies de un servidor HTTP(S), acepta las cookies usando códigos de control que cuando son enviados de vuelta a un servidor HTTP podrían hacer que el servidor devolviera respuestas 400. En efe... • http://seclists.org/fulldisclosure/2023/Jan/20 • CWE-20: Improper Input Validation CWE-1286: Improper Validation of Syntactic Correctness of Input •

CVSS: 4.3EPSS: 0%CPEs: 31EXPL: 1

28 Jun 2022 — A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and ... • http://seclists.org/fulldisclosure/2022/Oct/28 • CWE-770: Allocation of Resources Without Limits or Throttling •