Feature Request: Hardening the "Collaborators" section of Advisories #190673
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
Body
When adding collaborators to a security advisory, the typeahead dropdown feature shows non-project/org contributors as well.
This might allow an attacker to forge typosquatted usernames mimicking some core contributor name in the hope of accidentally gain access to undisclosed vulnerabilities and the ongoing conversation (which might also reveal details of other weaknesses, internal flawed processes, etc., as it's assumed to be private).
While this heavily relies on a luck/carelessness factor, at large scale attackers could just start creating variations of core contributor usernames from major projects and just wait until some mistake happens, or even accelerate that by stressing the security teams in those projects through false vulnerability reports.
I'd suggest that project/org members are shown with some visual cue, and/or that a confirmation is required to add a non-org/project user.
Beta Was this translation helpful? Give feedback.
All reactions