CVE-2023-51379 json
Incorrect Authorization for Issue Comments in GitHub Enterprise Server
published 2y ago modified 5mo ago also EUVD-2023-56100
- cvss
- 4.9
- 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 49%
- public exploits
- 0
- none known
Summary
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed issue comments to be updated with an improperly scoped token. This vulnerability did not allow unauthorized access to any repository content as it also required contents:write and issues:read permissions. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.17.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1.
Patch / fix
- GitHub Enterprise Server 3.7.19, 3.8.12, 3.9.7, 3.10.4, 3.11.1
Is CVE-2023-51379 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
Affected products
- GitHub Enterprise Server
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
docs.github.com
/en/enterprise-server@3.7/admin/release-notes#3.7.19
release-notes
-
docs.github.com
/en/enterprise-server@3.8/admin/release-notes#3.8.12
release-notes
-
docs.github.com
/en/enterprise-server@3.9/admin/release-notes#3.9.7
release-notes
-
docs.github.com
/en/enterprise-server@3.10/admin/release-notes#3.10.4
release-notes
-
docs.github.com
/en/enterprise-server@3.11/admin/release-notes#3.11.1
release-notes
Sources
- CVE List CVE-2023-51379
- NVD CVE-2023-51379
Fencer Intel 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.