GitHub Enterprise Server up to 3.8.11/3.9.5/3.10.3 Management Console privileges management

Summaryinfo

A vulnerability, which was classified as critical, has been found in GitHub Enterprise Server up to 3.8.11/3.9.5/3.10.3. Impacted is an unknown function of the component Management Console. Performing a manipulation results in privileges management. This vulnerability is identified as CVE-2023-46647. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in GitHub Enterprise Server up to 3.8.11/3.9.5/3.10.3 (Bug Tracking Software). This affects an unknown functionality of the component Management Console. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Improper privilege management in all versions of GitHub Enterprise Server allows users with authorized access to the management console with an editor role to escalate their privileges by making requests to the endpoint used for bootstrapping the instance. This vulnerability affected GitHub Enterprise Server version 3.8.0 and above and was fixed in version 3.8.12, 3.9.6, 3.10.3, and 3.11.0.

The weakness was released 12/22/2023 by Imre Rad. The advisory is shared at docs.github.com. This vulnerability is uniquely identified as CVE-2023-46647 since 10/24/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 3.8.12, 3.9.6, 3.10.3 or 3.11.0 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.8.0
• 3.8.1
• 3.8.2
• 3.8.3
• 3.8.4
• 3.8.5
• 3.8.6
• 3.8.7
• 3.8.8
• 3.8.9
• 3.8.10
• 3.8.11
• 3.9.0
• 3.9.1
• 3.9.2
• 3.9.3
• 3.9.4
• 3.9.5
• 3.10.0
• 3.10.1
• 3.10.2
• 3.10.3

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