Improper access control in GitHub Enterprise Server leading to unauthorized read access to private repository metadata
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 2.21.18, 2.22.10 and 3.0.4.
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's web authentication flow to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability was reported via the GitHub Bug Bounty program.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitHub | >=2.21 <2.21.18, >=2.22 <2.22.10, >=3.0 <3.0.4 | 2.21.18, 2.22.10, 3.0.4 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket