Skip to content

Latest commit

 

History

History
58 lines (41 loc) · 2.25 KB

SECURITY.md

File metadata and controls

58 lines (41 loc) · 2.25 KB

Security Policy

Security Announcements

Security fixes will be announced by posting them in the security changelog.

Scope and Supported Versions

The following versions of ClickHouse server are currently being supported with security updates:

Version Supported
1.x
18.x
19.x
20.x
21.1
21.2
21.3
21.4
21.5
21.6
21.7
21.8
21.9
21.10
21.11
21.12
22.1
22.2
22.3

Reporting a Vulnerability

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 [email protected].

When Should I Report a Vulnerability?

  • You think you discovered a potential security vulnerability in ClickHouse
  • You are unsure how a vulnerability affects ClickHouse

When Should I NOT Report a Vulnerability?

  • You need help tuning ClickHouse components for security
  • You need help applying security related updates
  • Your issue is not security related

Security Vulnerability Response

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.

Public Disclosure Timing

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 report date to disclosure date to be on the order of 7 days.