| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in GitHub Enterprise Server up to 3.11.16/3.12.10/3.13.5/3.14.2/3.15.1. The affected element is an unknown function. This manipulation causes code injection. This vulnerability is registered as CVE-2024-10001. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in GitHub Enterprise Server up to 3.11.16/3.12.10/3.13.5/3.14.2/3.15.1 and classified as critical. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A Code Injection vulnerability was identified in GitHub Enterprise Server that allowed attackers to inject malicious code into the query selector via the identity property in the message handling function. This enabled the exfiltration of sensitive data by manipulating the DOM, including authentication tokens. To execute the attack, the victim must be logged into GitHub and interact with the attacker controlled malicious webpage containing the hidden iframe. This vulnerability occurs due to an improper sequence of validation, where the origin check occurs after accepting the user-controlled identity property. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.11.16, 3.12.10, 3.13.5, 3.14.2, and 3.15.0. This vulnerability was reported via the GitHub Bug Bounty program.
The weakness was published by Matan Berson. The advisory is shared at docs.github.com. This vulnerability is known as CVE-2024-10001 since 10/15/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
Upgrading to version 3.11.16, 3.12.10, 3.13.5, 3.14.2 or 3.15.0 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.11.0
- 3.11.1
- 3.11.2
- 3.11.3
- 3.11.4
- 3.11.5
- 3.11.6
- 3.11.7
- 3.11.8
- 3.11.9
- 3.11.10
- 3.11.11
- 3.11.12
- 3.11.13
- 3.11.14
- 3.11.15
- 3.11.16
- 3.12.0
- 3.12.1
- 3.12.2
- 3.12.3
- 3.12.4
- 3.12.5
- 3.12.6
- 3.12.7
- 3.12.8
- 3.12.9
- 3.12.10
- 3.13.0
- 3.13.1
- 3.13.2
- 3.13.3
- 3.13.4
- 3.13.5
- 3.14.0
- 3.14.1
- 3.14.2
- 3.15.0
- 3.15.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
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.11.16/3.12.10/3.13.5/3.14.2/3.15.0
Timeline
10/15/2024 🔍01/29/2025 🔍
01/29/2025 🔍
09/05/2025 🔍
Sources
Advisory: docs.github.comResearcher: Matan Berson
Status: Confirmed
CVE: CVE-2024-10001 (🔍)
GCVE (CVE): GCVE-0-2024-10001
GCVE (VulDB): GCVE-100-294025
Entry
Created: 01/29/2025 23:12Updated: 09/05/2025 19:30
Changes: 01/29/2025 23:12 (69), 09/05/2025 19:30 (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.