First published: Fri Apr 02 2021(Updated: )
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.
Credit: product-cna@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitHub Enterprise Server | <2.21.18 | |
GitHub Enterprise Server | >=2.22.0<2.22.10 | |
GitHub Enterprise Server | >=3.0.0<3.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-22865 is an improper access control vulnerability in GitHub Enterprise Server.
CVE-2021-22865 allows access tokens generated from a GitHub App's web authentication flow to read private repository metadata via the REST API without having the appropriate permissions.
CVE-2021-22865 has a severity level of medium with a CVSS score of 6.5.
GitHub Enterprise Server versions 2.21.18 to 2.22.10 and versions 3.0.0 to 3.0.4 are affected by CVE-2021-22865.
To fix CVE-2021-22865, update your GitHub Enterprise Server to a version that is not affected by the vulnerability.