Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve vulnerability reporting process #22231

Open
Marcono1234 opened this issue Jun 2, 2024 · 1 comment
Open

Improve vulnerability reporting process #22231

Marcono1234 opened this issue Jun 2, 2024 · 1 comment
Assignees

Comments

@Marcono1234
Copy link

As part of reporting GHSA-973x-65j7-xcf4 for Aircompressor, I also tried to contact the maintainers here, and there were several problems:

Suggestions

  • Pick either reporting per mail, or GitHub private vulnerability reporting; or in case you want to support both, mention both in SECURITY.md then
    Personally I would recommend GitHub private vulnerability reporting because it simplifies some things, e.g.
    • lower risk of mails getting lost or being considered as spam
    • private collaboration and requesting of CVE before advisory is published
    • working together on a fix in a private fork
  • Actively check security@trino.io and the GitHub notifications for reports
  • Communication
    This is probably most important. Please confirm when you received the report, confirm if you were able to reproduce it. Ask if something is unclear or you disagree with the reporter (maybe there is a misunderstanding). Describe your planned schedule for the fix or publication of the advisory, or mention if you need more time. The reporter usually does not expect that you immediately publish a fix, but just wants to make sure you are aware of the vulnerability and a fix is published eventually.
    The worst thing is when you don't respond and the vulnerability is then either never fixed, or the reporter decides to publicly disclose it or directly contacts MITRE. And then you as maintainers are surprised by it and have to rush a fix for it, which risks being incomplete; and your users might be vulnerable in the meantime.
@mosabua
Copy link
Member

mosabua commented Jun 3, 2024

I am going to take this on @martint since I was already looking towards getting some openssf badges and such. Will work with you and @wendigo and others.

@mosabua mosabua self-assigned this Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants