First published: Wed Feb 14 2024(Updated: )
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an attacker to create new branches in public repositories and run arbitrary GitHub Actions workflows with permissions from the GITHUB_TOKEN. To exploit this vulnerability, an attacker would need access to the Enterprise Server. This vulnerability affected all versions of GitHub Enterprise Server after 3.8 and prior to 3.12, and was fixed in versions 3.9.10, 3.10.7, 3.11.5. 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 | >3.8<=3.12 | |
GitHub Enterprise Server | >=3.8.0<3.9.10 | |
GitHub Enterprise Server | >=3.10.0<3.10.7 | |
GitHub Enterprise Server | >=3.11.0<3.11.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-1482 is classified as a high severity vulnerability due to the potential for unauthorized branch creation and execution of GitHub Actions.
To fix CVE-2024-1482, upgrade your GitHub Enterprise Server to versions 3.9.10, 3.10.7, or 3.11.5, which contain the necessary patches.
CVE-2024-1482 affects GitHub Enterprise Server versions between 3.8.0 and 3.12 inclusive, specifically 3.8 to 3.11.x.
An attacker can exploit CVE-2024-1482 to create new branches in public repositories and execute arbitrary workflows with compromised GITHUB_TOKEN permissions.
CVE-2024-1482 is considered a remote vulnerability, as it can be exploited without physical access to the affected system.