p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in curl · Seite 4

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für curl: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 116

  1. ALPINE-CVE-2021-22901

    Hoch · CVSS 8.1Korrektur verfügbar

    ALPINE-CVE-2021-22901

    curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object m

    • Auf 7.77.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  2. ALPINE-CVE-2021-22898

    Niedrig · CVSS 3.1Korrektur verfügbar

    ALPINE-CVE-2021-22898

    curl 7.7 through 7.76.1 suffers from an information disclosure when the `-t` command line option, known as `CURLOPT_TELNETOPTIONS` in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.

    • Auf 7.77.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  3. ALPINE-CVE-2021-22890

    Niedrig · CVSS 3.7Korrektur verfügbar

    ALPINE-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 provid

    • Auf 7.76.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  4. ALPINE-CVE-2021-22876

    Mittel · CVSS 5.3Korrektur verfügbar

    ALPINE-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.

    • Auf 7.76.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  5. ALPINE-CVE-2020-8284

    Niedrig · CVSS 3.7Korrektur verfügbar

    ALPINE-CVE-2020-8284

    A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.

    • Auf 7.74.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  6. ALPINE-CVE-2019-3823

    Hoch · CVSS 7.5Korrektur verfügbar

    ALPINE-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.

    • Auf 7.64.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  7. ALPINE-CVE-2019-3822

    Kritisch · CVSS 9.8Korrektur verfügbar

    ALPINE-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

    • Auf 7.64.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  8. ALPINE-CVE-2018-16890

    Hoch · CVSS 7.5Korrektur verfügbar

    ALPINE-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.

    • Auf 7.64.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  9. ALPINE-CVE-2018-16842

    Kritisch · CVSS 9.1Korrektur verfügbar

    ALPINE-CVE-2018-16842

    Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

    • Auf 7.62.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  10. ALPINE-CVE-2018-16840

    Kritisch · CVSS 9.8Korrektur verfügbar

    ALPINE-CVE-2018-16840

    A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the `Curl_close()` function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

    • Auf 7.62.0-r0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →