Security fixes will be announced by posting them in the security changelog.
The following versions of ClickHouse server are currently being supported with security updates:
Version | Supported |
---|---|
24.4 | ✔️ |
24.3 | ✔️ |
24.2 | ✔️ |
24.1 | ❌ |
23.* | ❌ |
23.8 | ✔️ |
23.7 | ❌ |
23.6 | ❌ |
23.5 | ❌ |
23.4 | ❌ |
23.3 | ❌ |
23.2 | ❌ |
23.1 | ❌ |
22.* | ❌ |
21.* | ❌ |
20.* | ❌ |
19.* | ❌ |
18.* | ❌ |
1.* | ❌ |
We're extremely grateful for security researchers and users that report vulnerabilities to the ClickHouse Open Source Community. All reports are thoroughly investigated by developers.
To report a potential vulnerability in ClickHouse please send the details about it to security@clickhouse.com. We do not offer any financial rewards for reporting issues to us using this method. Alternatively, you can also submit your findings through our public bug bounty program hosted by Bugcrowd and be rewarded for it as per the program scope and rules of engagement.
Each report is acknowledged and analyzed by ClickHouse maintainers within 5 working days. As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated.
A public disclosure date is negotiated by the ClickHouse maintainers and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to 90 days. For a vulnerability with a straightforward mitigation, we expect the report date to disclosure date to be on the order of 7 days.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。