GitHub Enterprise Server up to 3.8.11/3.9.6/3.10.3/3.11.0 toctou
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
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 rated as problematic. This vulnerability affects unknown code. The manipulation leads to toctou. This vulnerability is documented as CVE-2023-6803. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is advised.
Details
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) and classified as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a toctou vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A race condition in GitHub Enterprise Server allows an outside collaborator to be added while a repository is being transferred. This vulnerability affected all versions of GitHub Enterprise Server since 3.8 and was fixed in version 3.8.12, 3.9.7, 3.10.4, and 3.11.1.
The weakness was released 12/22/2023 by Inspector-ambitious. The advisory is shared at docs.github.com. The identification of this vulnerability is CVE-2023-6803 since 12/13/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, 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.
Product
Type
Vendor
Name
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.5
VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.0
NVD Vector: 🔍
CNA Base Score: 5.8
CNA Vector (GitHub, Inc. (Products Only)): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: ToctouCWE: CWE-367 / CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Enterprise Server 3.8/3.8.12/3.9.7/3.10.4/3.11.1
Timeline
12/13/2023 🔍12/21/2023 🔍
12/22/2023 🔍
01/18/2024 🔍
Sources
Advisory: docs.github.comResearcher: Inspector-ambitious
Status: Confirmed
CVE: CVE-2023-6803 (🔍)
GCVE (CVE): GCVE-0-2023-6803
GCVE (VulDB): GCVE-100-248801
Entry
Created: 12/22/2023 00:36Updated: 01/18/2024 07:14
Changes: 12/22/2023 00:36 (51), 01/18/2024 07:14 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.