Responsible disclosure: improper access control in Gitlab private project.
Read OriginalThis article details a responsible disclosure case of an improper access control vulnerability in GitLab. A user removed from a private group could retain access to projects where their role was changed. The post outlines the vulnerability's impact, the lengthy and poorly communicated disclosure timeline with GitLab, and the eventual $2000 bounty award, while critiquing the process.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
Webinar Series – SQL Server Indexing
Koen Verbeeck
•
2 votes
2
Risks and Limitations of AI in the Life Sciences
Jeremy Howard
•
2 votes
3
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
2 votes
4
1M context is now generally available for Opus 4.6 and Sonnet 4.6
Simon Willison
•
1 votes
5
AI is my CMS
Chris Coyier
•
1 votes
6
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes