GitHub Enterprise Server up to 3.8.14/3.9.9/3.10.6/3.11.4 Management Console access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in GitHub Enterprise Server up to 3.8.14/3.9.9/3.10.6/3.11.4. This affects an unknown function of the component Management Console. The manipulation results in access control. This vulnerability was named CVE-2024-1372. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in GitHub Enterprise Server up to 3.8.14/3.9.9/3.10.6/3.11.4 (Bug Tracking Software). Affected is some unknown functionality of the component Management Console. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
A command injection vulnerability was identified in GitHub Enterprise Server that allowed an attacker with an editor role in the Management Console to gain admin SSH access to the appliance when configuring SAML settings. Exploitation of this vulnerability required access to the GitHub Enterprise Server instance and access to the Management Console with the editor role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.11.5, 3.10.7, 3.9.10, and 3.8.15. This vulnerability was reported via the GitHub Bug Bounty program https://bounty.github.com .
The weakness was presented 02/13/2024 by R31n. The advisory is shared for download at docs.github.com. This vulnerability is traded as CVE-2024-1372 since 02/08/2024. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 3.8.15, 3.9.10, 3.10.7 or 3.11.5 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
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.8.12
- 3.8.13
- 3.8.14
- 3.9.0
- 3.9.1
- 3.9.2
- 3.9.3
- 3.9.4
- 3.9.5
- 3.9.6
- 3.9.7
- 3.9.8
- 3.9.9
- 3.10.0
- 3.10.1
- 3.10.2
- 3.10.3
- 3.10.4
- 3.10.5
- 3.10.6
- 3.11.0
- 3.11.1
- 3.11.2
- 3.11.3
- 3.11.4
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.2
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.1
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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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.15/3.9.10/3.10.7/3.11.5
Timeline
02/08/2024 🔍02/13/2024 🔍
02/13/2024 🔍
03/05/2024 🔍
Sources
Advisory: docs.github.comResearcher: R31n
Status: Confirmed
CVE: CVE-2024-1372 (🔍)
GCVE (CVE): GCVE-0-2024-1372
GCVE (VulDB): GCVE-100-253668
Entry
Created: 02/13/2024 20:21Updated: 03/05/2024 01:53
Changes: 02/13/2024 20:21 (51), 03/05/2024 01:53 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.