CVE-2023-23762 json
Incorrect comparison vulnerability in GitHub Enterprise Server leading to commit smuggling
published 2023-04-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-27848
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
An incorrect comparison vulnerability was identified in GitHub Enterprise Server that allowed commit smuggling by displaying an incorrect diff. To do so, an attacker would need write access to the repository and be able to correctly guess the target branch before it’s created by the code maintainer. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.9 and was fixed in versions 3.4.18, 3.5.15, 3.6.11, 3.7.8, and 3.8.1. This vulnerability was reported via the GitHub Bug Bounty program.
Patch / fix
- GitHub Enterprise Server 3.4.18, 3.5.15, 3.6.11, 3.7.8, 3.8.1, 3.9.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- GitHub Enterprise Server
Classification
- Weakness
-
- CWE-697 Incorrect Comparison
References
-
docs.github.com
/en/enterprise-server@3.8/admin/release-notes#3.8.1
release-notes
-
docs.github.com
/en/enterprise-server@3.7/admin/release-notes#3.7.8
release-notes
-
docs.github.com
/en/enterprise-server@3.6/admin/release-notes#3.6.11
release-notes
-
docs.github.com
/en/enterprise-server@3.5/admin/release-notes#3.5.15
release-notes
-
docs.github.com
/en/enterprise-server@3.4/admin/release-notes#3.4.18
release-notes
Sources
- CVE List CVE-2023-23762
- NVD CVE-2023-23762
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.