First published: Tue Mar 07 2023(Updated: )
An information disclosure vulnerability was identified in GitHub Enterprise Server that allowed private repositories to be added to a GitHub Actions runner group via the API by a user who did not have access to those repositories, resulting in the repository names being shown in the UI. To exploit this vulnerability, an attacker would need access to the GHES instance, permissions to modify GitHub Actions runner groups, and successfully guess the obfuscated ID of private repositories. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.3.17, 3.4.12, 3.5.9, 3.6.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.3.0<3.3.17 | |
GitHub Enterprise Server | >=3.4.0<3.4.12 | |
GitHub Enterprise Server | >=3.5.0<3.5.9 | |
GitHub Enterprise Server | >=3.6.0<3.6.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-46257 is medium with a CVSS score of 4.3.
This vulnerability can be exploited by adding private repositories to a GitHub Actions runner group via the API without access to those repositories, resulting in the repository names being shown in the UI.
GitHub Enterprise Server versions 3.3.0 to 3.3.17, 3.4.0 to 3.4.12, 3.5.0 to 3.5.9, and 3.6.0 to 3.6.5 are affected by CVE-2022-46257.
You can find more information about CVE-2022-46257 in the GitHub Enterprise Server release notes.
The CWE ID for CVE-2022-46257 is CWE-668 and CWE-200.