Incomplete cache verification issue in GitHub Enterprise Server leading to exposure of private repo files
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.7epss 0.6%
exploitation probability
0.6%top 53% of all CVEs
observed exploitation
nono source reports it
An improper cache key vulnerability was identified in GitHub Enterprise Server that allowed an unauthorized actor to access private repository files through a public repository. To exploit this, an actor would need to already be authorized on the GitHub Enterprise Server instance, be able to create a public repository, and have a site administrator visit a specially crafted URL. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.6 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Affected products
GitHub · GitHub Enterprise ServerReferences
https://docs.github.com/en/enterprise-server%403.2/admin/release-notes#3.2.20https://docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.15https://docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.10https://docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.7https://docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.3