p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in haproxy

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 9

  1. CVE-2023-25725

    Kritisch · CVSS 9.1EPSS 5,45%Korrektur verfügbar

    CVE-2023-25725

    HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smuggling." The HTTP header parsers in HAProxy may accept empty header field names, which could be used to truncate the list of HTTP headers and thus make some headers disappear after being parsed and processed for HTTP/1.0 and HTTP/1.1. For HTTP/2 and HTTP/3, the impact is limited because the headers disappear before being parsed and processed, as if they had not been sent by the client. The fixed versions are 2.7.3, 2.6.9, 2.5.12, 2.4.22, 2.2.29, and 2.0.31.

    • Auf 1.8.8-1ubuntu0.13 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2020-11100

    Hoch · CVSS 8.8EPSS 61,59%Korrektur verfügbar

    CVE-2020-11100

    In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution.

    • Auf 1.8.8-1ubuntu0.10 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2019-18277

    Hoch · CVSS 7.5EPSS 10,07%Korrektur verfügbar

    CVE-2019-18277

    A flaw was found in HAProxy before 2.0.6. In legacy mode, messages featuring a transfer-encoding header missing the "chunked" value were not being correctly rejected. The impact was limited but if combined with the "http-reuse always" setting, it could be used to help construct an HTTP request smuggling attack against a vulnerable component employing a lenient parser that would ignore the content-length header as soon as it saw a transfer-encoding one (even if not entirely valid according to the specification).

    • Auf 1.8.8-1ubuntu0.7 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2018-20615

    Hoch · CVSS 7.5EPSS 4,46%Korrektur verfügbar

    CVE-2018-20615

    An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.

    • Auf 1.8.8-1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2018-20103

    Hoch · CVSS 7.5EPSS 6,59%Korrektur verfügbar

    CVE-2018-20103

    An issue was discovered in dns.c in HAProxy through 1.8.14. In the case of a compressed pointer, a crafted packet can trigger infinite recursion by making the pointer point to itself, or create a long chain of valid pointers resulting in stack exhaustion.

    • Auf 1.8.8-1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2018-20102

    Hoch · CVSS 7.5EPSS 4,15%Korrektur verfügbar

    CVE-2018-20102

    An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HAProxy through 1.8.14. Due to a missing check when validating DNS responses, remote attackers might be able read the 16 bytes corresponding to an AAAA record from the non-initialized part of the buffer, possibly accessing anything that was left on the stack, or even past the end of the 8193-byte buffer, depending on the value of accepted_payload_size.

    • Auf 1.8.8-1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2018-11469

    Mittel · CVSS 5.9EPSS 2,92%Korrektur verfügbar

    CVE-2018-11469

    Incorrect caching of responses to requests including an Authorization header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows attackers to achieve information disclosure via an unauthenticated remote request, related to the proto_http.c check_request_for_cacheability function.

    • Auf 1.8.8-1ubuntu0.1 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 →