108 results (0.011 seconds)

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 1

03 Feb 2024 — curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (*OCSP stapling*) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check. curl inadvertidamente mantuvo el ID de sesión SSL para las conexiones en su caché incluso cuando falló la prueba de verificación del estado (*OCSP stapling*). Una transferencia posterior al mismo nombre de host podría tener éxito si l... • https://curl.se/docs/CVE-2024-0853.html • CWE-295: Improper Certificate Validation •

CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 1

07 Dec 2023 — 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`,... • https://curl.se/docs/CVE-2023-46218.html • CWE-201: Insertion of Sensitive Information Into Sent Data •

CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 1

07 Dec 2023 — 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. Al guardar datos HSTS en un nombre de archivo excesivamente largo, curl podría terminar eliminando todo el contenido, haciendo que las solicitudes posteriores que utilicen ese archivo desconozcan el estado HSTS que de otro modo deberían usar. A security bypass flaw was found in Curl, which can be triggered by saving ... • https://curl.se/docs/CVE-2023-46219.html • CWE-311: Missing Encryption of Sensitive Data •

CVSS: 7.8EPSS: 70%CPEs: 12EXPL: 2

13 Sep 2023 — 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. Cuando curl recupera una respuesta HTTP, almacena los encabezados entrantes para que se pueda acceder a ellos más tarde a través de la API de encabezados libcur... • https://github.com/Smartkeyss/CVE-2023-38039 • CWE-770: Allocation of Resources Without Limits or Throttling •

CVSS: 3.3EPSS: 0%CPEs: 1EXPL: 0

22 Aug 2023 — Integer overflow vulnerability in tool_operate.c in curl 7.65.2 via a large value as the retry delay. NOTE: many parties report that this has no direct security impact on the curl user; however, it may (in theory) cause a denial of service to associated systems or networks if, for example, --retry-delay is misinterpreted as a value much smaller than what was intended. This is not especially plausible because the overflow only happens if the user was trying to specify that curl should wait weeks (or longer) ... • https://daniel.haxx.se/blog/2023/08/26/cve-2020-19909-is-everything-that-is-wrong-with-cves • CWE-190: Integer Overflow or Wraparound •

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

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

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) •