We sincerely request you to keep the vulnerability information confidential and responsibly disclose the vulnerabilities.
To report a vulnerability, please contact the Security Team: cncf-kubeedge-security@lists.cncf.io. You can email the Security Team with the security details and the details expected for KubeEdge bug reports.
The information of the Security Team members is described as follows:
| Name | |
|---|---|
| Kevin Wang (@kevin-wangzefeng) | wangzefeng@huawei.com |
| Fisher Xu (@fisherxu) | xufei40@huawei.com |
| Vincent Lin (@vincentgoat) | linguohui1@huawei.com |
| Wei Hu (@WillardHu) | wei.hu@daocloud.io |
The team will help diagnose the severity of the issue and determine how to address the issue. The reporter(s) can expect a response within 2 business day acknowledging the issue was received. If a response is not received within 2 business day, please reach out to any Security Team member directly to confirm receipt of the issue. We’ll try to keep you informed about our progress throughout the process.
- You think you discovered a potential security vulnerability in KubeEdge
- You are unsure how a vulnerability affects KubeEdge
- You need help tuning KubeEdge components for security
- You need help applying security related updates
- Your issue is not security related
If you think you discovered a vulnerability in another project that KubeEdge depends on, and that project has their own vulnerability reporting and disclosure process, please report it directly there.
The KubeEdge community will strictly handle the reporting vulnerability according to this procedure. The following flowchart shows the vulnerability handling process.
-
cncf-kubeedge-security@lists.cncf.io, is for reporting security concerns to the KubeEdge Security Team, who uses the list to privately discuss security issues and fixes prior to disclosure.
-
cncf-kubeedge-distrib-announce@lists.cncf.io, is for advance private information and vulnerability disclosure.
More details of group membership is managed here.
See the private-distributors-list for information on how KubeEdge distributors or vendors can apply to join this list.
KubeEdge versions are expressed as x.y.z, where x is the major version, y is the minor version, and z is the patch version, following Semantic Versioning terminology.
The KubeEdge project maintains release branches for the most recent three minor releases. Applicable fixes, including security fixes, may be backported to those three release branches, depending on severity and feasibility.
Our typical patch release cadence is every 3 months. Critical bug fixes may cause a more immediate release outside of the normal cadence. We also aim to not make releases during major holiday periods.
See the KubeEdge releases page for information on supported versions of KubeEdge.