ClickHouse/SECURITY.md

63 lines
2.3 KiB
Markdown
Raw Normal View History

2019-06-19 09:31:16 +00:00
# Security Policy
## Security Announcements
Security fixes will be announced by posting them in the [security changelog](https://clickhouse.tech/docs/en/whats-new/security-changelog/)
2019-06-19 09:31:16 +00:00
## Scope and Supported Versions
The following versions of ClickHouse server are currently being supported with security updates:
2019-06-19 09:31:16 +00:00
| Version | Supported |
| ------- | ------------------ |
| 1.x | :x: |
| 18.x | :x: |
2020-03-15 13:53:24 +00:00
| 19.x | :x: |
2020-07-06 10:41:32 +00:00
| 20.1 | :x: |
2021-08-23 13:08:08 +00:00
| 20.3 | :x: |
2020-10-01 11:00:35 +00:00
| 20.4 | :x: |
| 20.5 | :x: |
| 20.6 | :x: |
| 20.7 | :x: |
2021-08-23 13:08:08 +00:00
| 20.8 | :x: |
| 20.9 | :x: |
| 20.10 | :x: |
2021-08-23 13:08:08 +00:00
| 20.11 | :x: |
| 20.12 | :x: |
| 21.1 | :x: |
| 21.2 | :x: |
| 21.3 | ✅ |
| 21.4 | :x: |
| 21.5 | :x: |
| 21.6 | ✅ |
| 21.7 | ✅ |
| 21.8 | ✅ |
2019-06-19 09:31:16 +00:00
## Reporting a Vulnerability
We're extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
To report a potential vulnerability in ClickHouse please send the details about it to [clickhouse-feedback@yandex-team.com](mailto:clickhouse-feedback@yandex-team.com).
### 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 3 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 a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days.