CVE-2024-23689 is a high-severity (CVSS 8.8) CWE-209 vulnerability in com.clickhouse:clickhouse-client. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-23689 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ClickHouse Client Certificate Password Exposure
Real-World Exposure
com.clickhouse:clickhouse-client☕com.clickhouse:clickhouse-jdbc☕com.clickhouse:clickhouse-r2dbcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.clickhouse:clickhouse-client | all versions | 0.4.6 |
| ☕Maven | com.clickhouse:clickhouse-jdbc | all versions | 0.4.6 |
| ☕Maven | com.clickhouse:clickhouse-r2dbc | all versions | 0.4.6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.clickhouse:clickhouse-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.clickhouse:clickhouse-client to 0.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23689 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-23689 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-23689. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-23689 in your dependencies?
O3 detects CVE-2024-23689 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.