Improper access control in GitHub Enterprise Server leading to unauthorized changes to maintainer permissions on pull requests
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 1.0%
exploitation probability
1.0%top 41% of all CVEs
observed exploitation
nono source reports it
An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability affected all versions of GitHub Enterprise Server since 2.12.22 and was fixed in versions 2.20.24, 2.21.15, 2.22.7 and 3.0.1. This vulnerability was reported via the GitHub Bug Bounty program.
Affected products
GitHub · GitHub Enterprise ServerReferences
https://docs.github.com/en/enterprise-server%402.20/admin/release-notes#2.20.24https://docs.github.com/en/enterprise-server%402.21/admin/release-notes#2.21.15https://docs.github.com/en/enterprise-server%402.22/admin/release-notes#2.22.7https://docs.github.com/en/enterprise-server%403.0/admin/release-notes#3.0.1