GitHub Enterprise Server up to 3.3.16/3.4.11/3.5.8/3.6.4 API information disclosure

Summaryinfo

A vulnerability has been found in GitHub Enterprise Server up to 3.3.16/3.4.11/3.5.8/3.6.4 and classified as problematic. This vulnerability affects unknown code of the component API. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2022-46257. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.3.16/3.4.11/3.5.8/3.6.4 (Bug Tracking Software). It has been rated as problematic. This issue affects an unknown part of the component API. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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.

The weakness was presented 03/08/2023. The advisory is shared at docs.github.com. The identification of this vulnerability is CVE-2022-46257 since 11/28/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 3.3.17, 3.4.12, 3.5.9, 3.6.5 or 3.7 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.3.15
• 3.3.16
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9
• 3.4.10
• 3.4.11
• 3.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.5.4
• 3.5.5
• 3.5.6
• 3.5.7
• 3.5.8
• 3.6.0
• 3.6.1
• 3.6.2
• 3.6.3
• 3.6.4

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion