First published: Tue Jul 16 2024(Updated: )
A Cross-Site Request Forgery vulnerability in GitHub Enterprise Server allowed write operations on a victim-owned repository by exploiting incorrect request types. A mitigating factor is that the attacker would have to be a trusted GitHub Enterprise Server user, and the victim would have to visit a tag in the attacker's fork of their own repository. vulnerability affected all versions of GitHub Enterprise Server prior 3.14 and was fixed in version 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17. 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.
CVE-2024-5815 has been rated as a high-severity vulnerability due to the potential for unauthorized write operations on victim-owned repositories.
To fix CVE-2024-5815, update your GitHub Enterprise Server to version 3.9.17, 3.10.14, 3.11.12 or later versions that address this vulnerability.
CVE-2024-5815 affects users of GitHub Enterprise Server versions from 3.9.0 to 3.9.17, 3.10.0 to 3.10.14, 3.11.0 to 3.11.12, and 3.12.0 to 3.12.6, along with version 3.13.0.
CVE-2024-5815 is classified as a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to perform write operations on repositories.
An attacker exploiting CVE-2024-5815 must be a trusted user of the GitHub Enterprise Server that the victim also has access to.