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

Robot account update robot account without creator might cause privilege escalation #21026

Closed
stonezdj opened this issue Oct 10, 2024 · 1 comment
Assignees

Comments

@stonezdj
Copy link
Contributor

Steps to reproduce:

  1. Create a robot account A(project level), and grant permission robot (create/delete/update/list)
  2. Use the robot account A to create robot account B, B has permission robot (create/delete/update/list)
  3. Use the robot account B to create robot account C, C has permission robot (create/delete/update/list)
  4. Delete robot account B, then robot account A can update robot account C. and grant account C with excessive permission, such as accessory list

When the robot account's creator is removed, the update operation should be limited or disabled.

@wy65701436
Copy link
Contributor

close it as fixed by #21028

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants