GitHub Enterprise Server up to 3.6.2 API privileges management

Summaryinfo

A vulnerability has been found in GitHub Enterprise Server up to 3.2.19/3.3.14/3.4.9/3.5.6/3.6.2 and classified as critical. This affects an unknown function of the component API. This manipulation causes privileges management. This vulnerability is handled as CVE-2022-23737. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical was found in GitHub Enterprise Server up to 3.2.19/3.3.14/3.4.9/3.5.6/3.6.2 (Bug Tracking Software). Affected by this vulnerability is an unknown part of the component API. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An improper privilege management vulnerability was identified in GitHub Enterprise Server that allowed users with improper privileges to create or delete pages via the API. To exploit this vulnerability, an attacker would need to be added to an organization's repo with write permissions. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, and 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program.

The weakness was released 12/02/2022. It is possible to read the advisory at docs.github.com. This vulnerability is known as CVE-2022-23737 since 01/19/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3 or 3.7 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-28673). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9
• 3.2.10
• 3.2.11
• 3.2.12
• 3.2.13
• 3.2.14
• 3.2.15
• 3.2.16
• 3.2.17
• 3.2.18
• 3.2.19
• 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.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.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.5.4
• 3.5.5
• 3.5.6
• 3.6.0
• 3.6.1
• 3.6.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion