Join the chubaofs-users@groups.io group for emails about security and major announcements.
We’re extremely grateful for security researchers and users that report vulnerabilities to the ChubaoFS Open Source Community. All reports are thoroughly investigated by a dedicated committee of community volunteers called Product Security Committee.
To make a report, please email the private chubaofs-users@groups.io list with the security details and the details expected for all ChubaoFS bug reports.
- When discovered a potential security vulnerability in ChubaoFS
- When unsure how a vulnerability affects ChubaoFS
- When discovered a vulnerability in another project that ChubaoFS depends on
- Need help tuning ChubaoFS for security
- Need help applying security related updates
- When an issue is not security related
Each report is acknowledged and analyzed by Product Security Committee members within 3 working days. This will set off the Security Release Process.
Any vulnerability information shared with Product Security Committee stays within ChubaoFS project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
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 ChubaoFS Product Security Committee and the bug reporter. We prefer to fully disclose the bug as soon as possible once 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. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The ChubaoFS Product Security Committee holds the final say when setting a disclosure date.