Categories
CVE-2024-23689 high CVSS 8.8

Vulnerability in com.clickhouse:clickhouse-client (CVE-2024-23689)

Summary

Vulnerability in com.clickhouse:clickhouse-client (CVE-2024-23689). Risk of unauthorized operations or information disclosure. Exploitable via sslkey. Mitigation: upgrade to 0.4.6 or later.

Original description

The description as published by the source.

Exposure of sensitive information in exceptions in ClichHouse's clickhouse-r2dbc, com.clickhouse:clickhouse-jdbc, and com.clickhouse:clickhouse-client versions less than 0.4.6 allows unauthorized users to gain access to client certificate passwords via client exception logs. This occurs when 'sslkey' is specified and an exception, such as a ClickHouseException or SQLException, is thrown during database operations; the certificate password is then included in the logged exception message.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-23689 has been found in com.clickhouse:clickhouse-client.
Attackers can target a specific entry point like sslkey over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.8/10.
What to do: upgrade com.clickhouse:clickhouse-client to 0.4.6 or later.
If unsure, ask your IT team or search "com.clickhouse:clickhouse-client CVE-2024-23689" on the vendor's site.

CVE-2024-23689 (com.clickhouse:clickhouse-client) — CWE-209 / CVSS v3 8.8
Attack vector: local
Attack surface: sslkey
Patched: 0.4.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-209) exists in com.clickhouse:clickhouse-client. Attackers reach the vulnerable code path via sslkey.

📍 Affected scope

Check the vendor advisory for the affected versions of com.clickhouse:clickhouse-client. Attack surface: sslkey.

🔥 Severity

Severity: High (CVSS 8.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.4.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.clickhouse:clickhouse-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade com.clickhouse:clickhouse-client to 0.4.6

    ステージング環境で 0.4.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.clickhouse:clickhouse-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.6"}]}]
Maven com.clickhouse:clickhouse-jdbc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.6"}]}]
Maven com.clickhouse:clickhouse-r2dbc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details