title_wip

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/whats-new/security-changelog.md)

## Fixed in ClickHouse v25.1.5.5, 2025-01-05[​](#fixed-in-clickhouse-release-2025-01-05 "Direct link to Fixed in ClickHouse v25.1.5.5, 2025-01-05")

### [CVE-2025-1385](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-5phv-x8x4-83x5)[​](#CVE-2025-1385 "Direct link to CVE-2025-1385")

When the library bridge feature is enabled, the clickhouse-library-bridge exposes an HTTP API on localhost. This allows clickhouse-server to dynamically load a library from a specified path and execute it in an isolated process. Combined with the ClickHouse table engine functionality that permits file uploads to specific directories, a misconfigured server can be exploited by an attacker with privileges to access both table engines, allowing them to execute arbitrary code on the ClickHouse server.

Fix has been pushed to the following open-source versions: v24.3.18.6, v24.8.14.27, v24.11.5.34, v24.12.5.65, v25.1.5.5

ClickHouse Cloud is unaffected by this vulnerability.

Credits: [Arseniy Dugin](https://github.com/ZerLes)

## Fixed in ClickHouse v24.5, 2024-08-01[​](#fixed-in-clickhouse-release-2024-08-01 "Direct link to Fixed in ClickHouse v24.5, 2024-08-01")

### [CVE-2024-6873](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-432f-r822-j66f)[​](#CVE-2024-6873 "Direct link to CVE-2024-6873")

It is possible to redirect the execution flow of the ClickHouse server process from an unauthenticated vector by sending a specially crafted request to the ClickHouse server native interface. This redirection is limited to what is available within a 256-byte range of memory at the time of execution. This vulnerability was identified through our Bugbounty program and no known Proof of Concept Remote Code Execution (RCE) code has been produced or exploited.

Fix has been pushed to the following open-source versions: v23.8.15.35-lts, v24.3.4.147-lts, v24.4.2.141-stable, v24.5.1.1763, v24.6.1.4423-stable

ClickHouse Cloud uses different versioning and a fix for this vulnerability was applied to all instances running v24.2 onward.

Credits: malacupa (Independent researcher)

## Fixed in ClickHouse v24.1, 2024-01-30[​](#fixed-in-clickhouse-release-24-01-30 "Direct link to Fixed in ClickHouse v24.1, 2024-01-30")

### [CVE-2024-22412](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-45h5-f7g3-gr8r)[​](#CVE-2024-22412 "Direct link to CVE-2024-22412")

When toggling between user roles while using ClickHouse with query cache enabled, there is a risk of obtaining inaccurate data. ClickHouse advises users with vulnerable versions of ClickHouse not to use the query cache when their application dynamically switches between various roles.

Fix has been pushed to the following open-source versions: v24.1.1.2048, v24.1.8.22-stable, v23.12.6.19-stable, v23.8.12.13-lts, v23.3.22.3-lts

ClickHouse Cloud uses different versioning and a fix for this vulnerability was applied at v24.0.2.54535.

Credits: Evan Johnson and Alan Braithwaite from Runreveal team - More information can be found on [their blog post](https://blog.runreveal.com/cve-2024-22412-behind-the-bug-a-classic-caching-problem-in-the-clickhouse-query-cache/).

## Fixed in ClickHouse v23.10.5.20, 2023-11-26[​](#fixed-in-clickhouse-release-23-10-5-20-2023-11-26 "Direct link to Fixed in ClickHouse v23.10.5.20, 2023-11-26")

### [CVE-2023-47118](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-g22g-p6q2-x39v)[​](#CVE-2023-47118 "Direct link to CVE-2023-47118")

A heap buffer overflow vulnerability affecting the native interface running by default on port 9000/tcp. An attacker, by triggering a bug in the T64 compression codec, can cause the ClickHouse server process to crash. This vulnerability can be exploited without the need to authenticate.

Fix has been pushed to the following open-source versions: v23.10.2.13, v23.9.4.11, v23.8.6.16, v23.3.16.7

ClickHouse Cloud uses different versioning and a fix for this vulnerability was applied at v23.9.2.47475.

Credits: malacupa (Independent researcher)

### [CVE-2023-48298](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-qw9f-qv29-8938)[​](#CVE-2023-48298 "Direct link to CVE-2023-48298")

An integer underflow vulnerability in the FPC compressions codec. An attacker can use it to cause the ClickHouse server process to crash. This vulnerability can be exploited without the need to authenticate.

Fix has been pushed to the following open-source versions: v23.10.4.25, v23.9.5.29, v23.8.7.24, v23.3.17.13.

ClickHouse Cloud uses different versioning and a fix for this vulnerability was applied at v23.9.2.47475.

Credits: malacupa (Independent researcher)

### [CVE-2023-48704](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-5rmf-5g48-xv63)[​](#CVE-2023-48704 "Direct link to CVE-2023-48704")

A heap buffer overflow vulnerability affecting the native interface running by default on port 9000/tcp. An attacker, by triggering a bug in the Gorilla codec, can cause the ClickHouse server process to crash. This vulnerability can be exploited without the need to authenticate.

Fix has been pushed to the following open-source versions: v23.10.5.20, v23.9.6.20, v23.8.8.20, v23.3.18.15.

ClickHouse Cloud uses different versioning and a fix for this vulnerability was applied at v23.9.2.47551.

Credits: malacupa (Independent researcher)

## Fixed in ClickHouse 22.9.1.2603, 2022-09-22[​](#fixed-in-clickhouse-release-22-9-1-2603-2022-9-22 "Direct link to Fixed in ClickHouse 22.9.1.2603, 2022-09-22")

### CVE-2022-44011[​](#CVE-2022-44011 "Direct link to CVE-2022-44011")

A heap buffer overflow issue was discovered in ClickHouse server. A malicious user with ability to load data into ClickHouse server could crash the ClickHouse server by inserting a malformed CapnProto object.

Fix has been pushed to version 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, 22.3.12.19

Credits: Kiojj (independent researcher)

### CVE-2022-44010[​](#CVE-2022-44010 "Direct link to CVE-2022-44010")

A heap buffer overflow issue was discovered in ClickHouse server. An attacker could send a specially crafted HTTP request to the HTTP Endpoint (listening on port 8123 by default), causing a heap-based buffer overflow that crashes the ClickHouse server process. This attack does not require authentication.

Fix has been pushed to version 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, 22.3.12.19

Credits: Kiojj (independent researcher)

## Fixed in ClickHouse 21.10.2.15, 2021-10-18[​](#fixed-in-clickhouse-release-21-10-2-215-2021-10-18 "Direct link to Fixed in ClickHouse 21.10.2.15, 2021-10-18")

### CVE-2021-43304[​](#cve-2021-43304 "Direct link to 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.

Credits: JFrog Security Research Team

### CVE-2021-43305[​](#cve-2021-43305 "Direct link to 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.

Credits: JFrog Security Research Team

### CVE-2021-42387[​](#cve-2021-42387 "Direct link to 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.

Credits: JFrog Security Research Team