CVE-2022-23738: Incomplete cache verification issue in GitHub Enterprise Server leading to exposure of private repo files
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2022-23738?
CVE-2022-23738 is an improper cache key vulnerability in GitHub Enterprise Server.
What is the severity of CVE-2022-23738?
The severity of CVE-2022-23738 is medium, with a severity value of 5.7.
How does CVE-2022-23738 impact GitHub Enterprise Server?
CVE-2022-23738 allows an unauthorized actor to access private repository files through a public repository on GitHub Enterprise Server.
Which versions of GitHub Enterprise Server are affected by CVE-2022-23738?
GitHub Enterprise Server versions 3.2.0 to 3.2.20, 3.3.0 to 3.3.15, 3.4.0 to 3.4.10, 3.5.0 to 3.5.7, and 3.6.0 to 3.6.3 are affected by CVE-2022-23738.
How can I fix CVE-2022-23738?
To fix CVE-2022-23738, it is recommended to upgrade GitHub Enterprise Server to a version that includes a fix for the vulnerability.