GitHub Enterprise Server
SSH certificate authentication bypass in GitHub Enterprise Server
An SSH certificate authentication bypass vulnerability in GitHub Enterprise Server allowed an authenticated organization member to read and modify another user's private repositories within the trusted certificate authority's scope. Exploitation required an instance using built-in authentication and a valid certificate issued to the attacker by a trusted SSH certificate authority. This vulnerability affected supported GitHub Enterprise Server releases prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.19.0, < 3.19.*
- >= 3.20.0, < 3.20.*
- >= 3.21.0, < 3.21.*
- >= 3.22.0, < 3.22.*
Fixed in 3.19.*, 3.19.16, 3.20.*, 3.20.12, 3.21.*, 3.21.10, 3.22.*, 3.22.5
Mitigation
Upgrade Enterprise Server to 3.19.* or 3.19.16 or 3.20.* or 3.20.12 or 3.21.* or 3.21.10 or 3.22.* or 3.22.5 or later.
References
- Release notes docs.github.com/en/enterprise-server@3.19/admin/rel…
- Release notes docs.github.com/en/enterprise-server@3.20/admin/rel…
- Release notes docs.github.com/en/enterprise-server@3.21/admin/rel…
1 more
- Release notes docs.github.com/en/enterprise-server@3.22/admin/rel…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.