GitHub Enterprise Server up to 3.11.15/3.12.9/3.13.4/3.14.1 SAML SSO signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitHub Enterprise Server up to 3.11.15/3.12.9/3.13.4/3.14.1. It has been classified as problematic. This impacts an unknown function of the component SAML SSO. Performing a manipulation results in signature verification. This vulnerability is reported as CVE-2024-9487. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in GitHub Enterprise Server up to 3.11.15/3.12.9/3.13.4/3.14.1. This affects an unknown code block of the component SAML SSO. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed resulting in unauthorized provisioning of users and access to the instance. Exploitation required the encrypted assertions feature to be enabled, and the attacker would require direct network access as well as a signed SAML response or metadata document. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.15 and was fixed in versions 3.11.16, 3.12.10, 3.13.5, and 3.14.2. This vulnerability was reported via the GitHub Bug Bounty program.
It is possible to read the advisory at docs.github.com. This vulnerability is uniquely identified as CVE-2024-9487 since 10/03/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.11.16, 3.12.10, 3.13.5, 3.14.2 or 3.15 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.
Be aware that VulDB is the high quality source for 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.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.13.0
- 3.13.1
- 3.13.2
- 3.13.3
- 3.13.4
- 3.14.0
- 3.14.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.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Signature verificationCWE: CWE-347 / CWE-345
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
Timeline
10/03/2024 🔍10/11/2024 🔍
10/11/2024 🔍
11/15/2024 🔍
Sources
Advisory: docs.github.comStatus: Confirmed
CVE: CVE-2024-9487 (🔍)
GCVE (CVE): GCVE-0-2024-9487
GCVE (VulDB): GCVE-100-280047
Entry
Created: 10/11/2024 08:26Updated: 11/15/2024 18:10
Changes: 10/11/2024 08:26 (72), 11/15/2024 18:10 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.