First published: Tue Jul 16 2024(Updated: )
An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed a suspended GitHub App to retain access to the repository via a scoped user access token. This was only exploitable in public repositories while private repositories were not impacted. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.9.17, 3.10.14, 3.11.12, 3.12.6, 3.13.1. This vulnerability was reported via the GitHub Bug Bounty program.
Credit: product-cna@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitHub Enterprise | >=3.9.0<3.9.17 | |
GitHub Enterprise | >=3.10.0<3.10.14 | |
GitHub Enterprise | >=3.11.0<3.11.12 | |
GitHub Enterprise | >=3.12.0<3.12.6 | |
GitHub Enterprise | =3.13.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-5816 is classified as high due to the risk of unauthorized access to repositories.
To fix CVE-2024-5816, it is recommended to update GitHub Enterprise Server to version 3.10.15 or later, 3.11.12 or later, 3.12.6 or later, or version 3.13.0.
CVE-2024-5816 affects GitHub Enterprise Server versions 3.9.0 to 3.9.17, 3.10.0 to 3.10.14, 3.11.0 to 3.11.12, 3.12.0 to 3.12.6, and 3.13.0.
No, private repositories are not impacted by CVE-2024-5816; the vulnerability only affects public repositories.
CVE-2024-5816 is an Incorrect Authorization vulnerability that allows a suspended GitHub App to retain access through a scoped user access token.