[Docs][Security] Clarify reporter credit and CVE publication timing (#55476)
Signed-off-by: Juan Pérez de Algaba <jperezde@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
co-authored by
Cursor
parent
86aca66191
commit
08426d51ef
@@ -44,6 +44,13 @@ to discuss security-related topics. However, please do not disclose any
|
||||
vulnerabilities in this channel. If you need to report a vulnerability, please
|
||||
use the GitHub security advisory system or contact a VMT member privately.
|
||||
|
||||
## Reporter Credit
|
||||
|
||||
Credit for a vulnerability is given only to the first reporter. Subsequent
|
||||
reports of the same issue are not credited, including independent
|
||||
rediscoveries. Duplicate and AI-generated submissions are common enough that
|
||||
crediting every submitter is not practical.
|
||||
|
||||
## Vulnerability Disclosure
|
||||
|
||||
The process for disclosing vulnerabilities is the following:
|
||||
@@ -52,10 +59,10 @@ The process for disclosing vulnerabilities is the following:
|
||||
vulnerability.
|
||||
- The VMT will coordinate with the reporter and project maintainers to prepare a
|
||||
security advisory that adequately describes the vulnerability and its impact.
|
||||
- The VMT will coordinate with the project maintainers to publish a fix and
|
||||
release an update that includes that fix.
|
||||
- The VMT will publish the security advisory on GitHub. Release notes will be
|
||||
updated to include a reference to the security advisory.
|
||||
- After the advisory has been accepted, a CVE is requested when a patch for the
|
||||
issue is merged.
|
||||
- The advisory is published on GitHub when the fix lands in a vLLM release.
|
||||
Release notes will be updated to include a reference to the security advisory.
|
||||
|
||||
The VMT and project maintainers will work to minimize the amount of time in
|
||||
between disclosing any public information about the vulnerability and making a
|
||||
|
||||
Reference in New Issue
Block a user