mirror of
https://github.com/ceph/ceph
synced 2024-12-23 03:44:23 +00:00
50 lines
2.7 KiB
ReStructuredText
50 lines
2.7 KiB
ReStructuredText
Vulnerability Management Process
|
|
================================
|
|
|
|
#. The report will be acknowledged within three business days.
|
|
#. The team will investigate and update the email thread with relevant
|
|
information and may ask for additional information or guidance
|
|
surrounding the reported issue.
|
|
#. If the team does not confirm the report, no further action will be
|
|
taken and the issue will be closed.
|
|
#. If the team confirms the report, a unique CVE identifier will be
|
|
assigned and shared with the reporter. The team will take action to
|
|
fix the issue.
|
|
#. In cases in which a reporter has not chosen a date to disclose the
|
|
vulnerability, a Ceph security team member will work with the list members
|
|
to coordinate a release date (CRD). The agreed upon release date
|
|
will be shared with the reporter.
|
|
#. The vulnerability disclosure / release date is set excluding Friday and
|
|
holiday periods.
|
|
#. Embargoes are preferred for "Critical" and "High impact" issues. Embargoes
|
|
should not be in effect for more than 90 days from the date of the
|
|
confirmation of the vulnerability, except under unusual circumstances. For
|
|
"Low" and "Moderate" issues with limited impact and an easy workaround (or
|
|
in cases where an issue is already public), a unique CVE identifier will be
|
|
assigned and then a standard patch release process will be followed to fix
|
|
the vulnerability.
|
|
#. Medium and Low severity issues will be released as part of the next
|
|
standard release cycle, with at least a 7 days advanced
|
|
notification to the list members prior to the release date. The CVE
|
|
fix details will be included in the release notes, which will be
|
|
linked in the public announcement.
|
|
#. Commits will be handled in a private repository for review and
|
|
testing and a new patch version will be released from this private
|
|
repository.
|
|
#. If a vulnerability is unintentionally already fixed in the public
|
|
repository, a few days are given to downstream stakeholders/vendors
|
|
to prepare for updating before the public disclosure.
|
|
#. An announcement will be made disclosing the vulnerability. The
|
|
fastest place to receive security announcements is via the
|
|
`ceph-announce@ceph.io <ceph-announce@ceph.io>`_ or
|
|
`oss-security@lists.openwall.com <oss-security@lists.openwall.com>`_ mailing
|
|
lists. (These lists are low-traffic).
|
|
|
|
If the report is considered embargoed, we ask you to not disclose the
|
|
vulnerability before it has been fixed and announced, unless you
|
|
received a response from the Ceph security team that you can do
|
|
so. This holds true until the public disclosure date that was agreed
|
|
upon by the list. Thank you for improving the security of Ceph and its
|
|
ecosystem. Your efforts and responsible disclosure are greatly
|
|
appreciated and will be acknowledged.
|