Use this section to tell people about which versions of your project are currently being supported with security updates.
| Version | Supported |
|---|---|
| 3.2.x | ✅ |
| 3.1.x | ✅ |
| 3.0.x | ✅ |
| 2.1.x | ✅ |
| < 2.1.x | ❌ |
To ensure KubeSphere security, a security vulnerability disclosure and response process is adopted. And the security team is set up in KubeSphere community, also any issue and PR is welcome for every contributors.
The primary goal of this process is to reduce the total exposure time of users to publicly known vulnerabilities. To quickly fix vulnerabilities of KubeSphere, the security team is responsible for the entire vulnerability management process, including internal communication and external disclosure.
If you find a vulnerability or encounter a security incident involving vulnerabilities of KubeSphere, please report it as soon as possible to the KubeSphere security team ([email protected]).
Please kindly help provide as much vulnerability information as possible in the following format:
-
Issue title(Please add 'Security' lable)*:
-
Overview*:
-
Affected components and version number*:
-
CVE number (if any):
-
Vulnerability verification process*:
-
Contact information*:
The asterisk (*) indicates the required field.
The KubeSphere security team will confirm the vulnerabilities and contact you within 2 working days after your submission.
We will publicly thank you after fixing the security vulnerability. To avoid negative impact, please keep the vulnerability confidential until we fix it. We would appreciate it if you could obey the following code of conduct:
The vulnerability will not be disclosed until KubeSphere releases a patch for it.
The details of the vulnerability, for example, exploits code, will not be disclosed.