LiveActive security incident?Get immediate response
CVE Record

CVE-2024-23689: ClickHouse Client Certificate Password Exposure

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Certain ClickHouse Java clients could put a client certificate password into exception log messages. If those logs are readable by unauthorized people, the password could be used to compromise database client authentication. The issue is fixed in version 0.4.6 according to the referenced release and advisories.

Executive priority

Treat this as a high-priority secrets exposure issue where affected ClickHouse Java clients are in use. Prioritize upgrade and log review, especially in environments with shared logging access.

Technical view

CVE-2024-23689 is a CWE-209 sensitive-information exposure in clickhouse-r2dbc, clickhouse-jdbc, and clickhouse-client before 0.4.6. When sslkey is configured and ClickHouseException or SQLException is thrown, the client certificate password may appear in logged exception messages.

Likely exposure

Exposure is most likely in Java applications using affected ClickHouse client libraries before 0.4.6, configured with sslkey and logging database exceptions to local or centralized logs accessible beyond trusted operators.

Exploitation context

The bundle does not identify active exploitation, and KEV is false. Risk depends on whether exceptions occurred, whether logs captured the password, and who can read those logs.

Researcher notes

The strongest evidence is vendor and GitHub advisory material. The bundle’s affected-version fields appear sparse, but the narrative consistently identifies versions before 0.4.6 as affected. No cited source proves exploitation in the wild.

Mitigation direction

  • Upgrade clickhouse-r2dbc, clickhouse-jdbc, and clickhouse-client to version 0.4.6 or later.
  • Review vendor advisory and release notes before deploying the fix.
  • Restrict access to application, database, and centralized exception logs.
  • Rotate affected client certificate passwords if logs were accessible to unauthorized users.
  • Purge or quarantine exposed logs according to retention and incident-response policy.

Validation and detection

  • Inventory applications using com.clickhouse ClickHouse Java client packages.
  • Confirm deployed dependency versions are 0.4.6 or later.
  • Identify deployments using sslkey with client certificate authentication.
  • Review exception logs for accidental certificate password exposure.
  • Verify log access controls in local and centralized logging systems.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-209: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-23689 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-23689Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorcom.clickhouse:clickhouse-r2dbccom.clickhouse:clickhouse-r2dbc, 0unaffected
Unknown vendorcom.clickhouse:clickhouse-jdbccom.clickhouse:clickhouse-jdbc, 0unaffected
Unknown vendorcom.clickhouse:clickhouse-clientcom.clickhouse:clickhouse-client, 0unaffected
Weakness

CWE details

CWE-209

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-209 · source CWE mapping

Generation of Error Message Containing Sensitive Information

Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs