Missing authorization in GitHub Enterprise Server allowed repository writers to replace default branches via GraphQL
What fixes it
- 3.18.*Enterprise ServerCVE List
- 3.19.*Enterprise ServerCVE List
- 3.20.*Enterprise ServerCVE List
- 3.21.*Enterprise ServerCVE List
- 3.22.*Enterprise ServerCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed a repository collaborator with write access to delete the current default branch through the GraphQL API and cause an attacker-controlled branch to become the new default. In repositories that required pull-request review but did not restrict branch deletion, this bypassed the review requirement and caused fresh clones and default-branch API requests to use attacker-controlled content. This vulnerability affected supported GitHub Enterprise Server releases in the 3.18, 3.19, 3.20, 3.21, and 3.22 series and was fixed in versions 3.18.16, 3.19.13, 3.20.9, 3.21.7, and 3.22.2. This vulnerability was reported via the GitHub Bug Bounty program.
Text from CVE List
Affected versions 5
- Enterprise Serveraffected: 3.18.0 before 3.18.*CVE List
- Enterprise Serveraffected: 3.19.0 before 3.19.*CVE List
- Enterprise Serveraffected: 3.20.0 before 3.20.*CVE List
- Enterprise Serveraffected: 3.21.0 before 3.21.*CVE List
- Enterprise Serveraffected: 3.22.0 before 3.22.*CVE List
References 5
- docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.16Fixvia CVE List
- docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.13Fixvia CVE List
- docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.9Fixvia CVE List
- docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.7Fixvia CVE List
- docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.2Fixvia CVE List