GitHub Enterprise Server up to 3.8.11/3.9.6/3.10.3/3.11.0 GraphQL Mutation toctou

Summaryinfo

A vulnerability was found in GitHub Enterprise Server up to 3.8.11/3.9.6/3.10.3/3.11.0. It has been classified as problematic. This impacts an unknown function of the component GraphQL Mutation Handler. This manipulation causes toctou. This vulnerability is registered as CVE-2023-6690. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.8.11/3.9.6/3.10.3/3.11.0 (Bug Tracking Software). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component GraphQL Mutation Handler. The manipulation with an unknown input leads to a toctou vulnerability. The CWE definition for the vulnerability is CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A race condition in GitHub Enterprise Server allowed an existing admin to maintain permissions on transferred repositories by making a GraphQL mutation to alter repository permissions during the transfer. This vulnerability affected GitHub Enterprise Server version 3.8.0 and above and was fixed in version 3.8.12, 3.9.7, 3.10.4, and 3.11.1.

The weakness was published 12/22/2023 by Inspector-ambitious. The advisory is shared at docs.github.com. This vulnerability is known as CVE-2023-6690 since 12/11/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

Upgrading to version 3.8.0, 3.8.12, 3.9.7, 3.10.4 or 3.11.1 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 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
• 3.9.0
• 3.9.1
• 3.9.2
• 3.9.3
• 3.9.4
• 3.9.5
• 3.9.6
• 3.10
• 3.10.0
• 3.10.1
• 3.10.2
• 3.10.3
• 3.11.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion