CVE-2024-23689
Clickhouse Java Libraries information disclosure
- Published19 Jan 2024
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/advisories/GHSA-g8ph-74m6-8m7r
- https://github.com/ClickHouse/clickhouse-java/issues/1331
- https://github.com/ClickHouse/clickhouse-java/pull/1334
- https://github.com/ClickHouse/clickhouse-java/releases/tag/v0.4.6
- https://github.com/ClickHouse/clickhouse-java/security/advisories/GHSA-g8ph-74m6-8m7r
- https://vulncheck.com/advisories/vc-advisory-GHSA-g8ph-74m6-8m7r
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-23689 being actively exploited?
CVE-2024-23689 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.68%.
How severe is CVE-2024-23689?
CVE-2024-23689 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.68% probability of exploitation.
Which products are affected by CVE-2024-23689?
Affected products include Clickhouse Java Libraries.
How do I fix CVE-2024-23689?
Upgrade affected software to a fixed version, for example Clickhouse Java Libraries 0.4.6 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-23689 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.