p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in clickhouse

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

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 9

  1. CVE-2024-22412

    Niedrig · CVSS 2.4EPSS 0,59%Keine Korrektur veröffentlicht

    ClickHouse's Role-based Access Control is bypassed when query caching is enabled.

    ClickHouse is an open-source column-oriented database management system. A bug exists in the cloud ClickHouse offering prior to version 24.0.2.54535 and in github.com/clickhouse/clickhouse version 23.1. Query caching bypasses the role based access controls and the policies being enforced on roles. In affected versions, the query cache only respects separate users, however this is not documented and not expected behavior. People relying on ClickHouse roles can have their access control lists bypassed if they are using query caching. Attackers who have control of a role could guess queries and see data they shouldn't have access to. Version 24.

    Veröffentlicht Aktualisiert
  2. CVE-2022-44011

    Mittel · CVSS 6.5EPSS 0,7%Keine Korrektur veröffentlicht

    CVE-2022-44011

    An issue was discovered in ClickHouse before 22.9.1.2603. An authenticated user (with the ability to load data) could cause a heap buffer overflow and crash the server by inserting a malformed CapnProto object. The fixed versions are 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, and 22.3.12.19.

    Veröffentlicht Aktualisiert
  3. CVE-2022-44010

    Hoch · CVSS 7.5EPSS 0,97%Keine Korrektur veröffentlicht

    CVE-2022-44010

    An issue was discovered in ClickHouse before 22.9.1.2603. An attacker could send a crafted HTTP request to the HTTP Endpoint (usually listening on port 8123 by default), causing a heap-based buffer overflow that crashes the process. This does not require authentication. The fixed versions are 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, and 22.3.12.19.

    Veröffentlicht Aktualisiert
  4. CVE-2021-43305

    Hoch · CVSS 8.8EPSS 1,67%Korrektur verfügbar

    CVE-2021-43305

    Heap buffer overflow in Clickhouse's LZ4 compression codec when parsing a malicious query. There is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits. This issue is very similar to CVE-2021-43304, but the vulnerable copy operation is in a different wildCopy call.

    • Auf 18.16.1+ds-7.3 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2021-43304

    Hoch · CVSS 8.8EPSS 1,67%Korrektur verfügbar

    CVE-2021-43304

    Heap buffer overflow in Clickhouse's LZ4 compression codec when parsing a malicious query. There is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopy<copy_amount>(op, ip, copy_end), don’t exceed the destination buffer’s limits.

    • Auf 18.16.1+ds-7.3 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2021-42388

    Hoch · CVSS 8.1EPSS 1,57%Korrektur verfügbar

    CVE-2021-42388

    Heap out-of-bounds read in Clickhouse's LZ4 compression codec when parsing a malicious query. As part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value ('offset') is read from the compressed data. The offset is later used in the length of a copy operation, without checking the lower bounds of the source of the copy operation.

    • Auf 18.16.1+ds-7.3 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2021-42387

    Hoch · CVSS 8.1EPSS 1,57%Korrektur verfügbar

    CVE-2021-42387

    Heap out-of-bounds read in Clickhouse's LZ4 compression codec when parsing a malicious query. As part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value ('offset') is read from the compressed data. The offset is later used in the length of a copy operation, without checking the upper bounds of the source of the copy operation.

    • Auf 18.16.1+ds-7.3 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 →