Technical impact
An incorrect authorization flaw allows an authenticated user whose numeric user ID matches an enterprise’s numeric ID to manage that enterprise’s GitHub Apps and generate private keys without being a member of the enterprise. The ownership checks compare numeric IDs without validating account type, enabling an attacker to claim App ownership. Exploitation requires control or hijacking of a session for the colliding user account, after which the attacker can use the generated private key to authenticate as the App and read or modify repositories where the App is installed, limited by the App’s granted permissions. This flaw represents a significant privilege escalation that can grant unauthorized access to organizational code and secrets.
Affected Systems
GitHub Enterprise Server versions prior to 3.23 are affected. The vulnerability was fixed in releases 3.19.16, 3.20.12, 3.21.10, and 3.22.5, and will be present in any earlier supported release.
Risk and Exploitability
The CVSS score of 7.4 indicates high severity, and the flaw is not listed in the CISA KEV catalog. Exploitation requires an authenticated session for a colliding user ID, so the attack surface is limited to users whose numeric ID matches an enterprise ID; however, the availability of such collisions and the ability to generate a private key increases the risk to repositories installed for the app. The EPSS score of < 1% suggests a very low probability of exploitation, yet the impact of successful exploitation remains high.