First published: Tue Nov 01 2022(Updated: )
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.
Credit: product-cna@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitHub Enterprise Server | >=3.2.0<3.2.20 | |
GitHub Enterprise Server | >=3.3.0<3.3.15 | |
GitHub Enterprise Server | >=3.4.0<3.4.10 | |
GitHub Enterprise Server | >=3.5.0<3.5.7 | |
GitHub Enterprise Server | >=3.6.0<3.6.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-23738 is an improper cache key vulnerability in GitHub Enterprise Server.
The severity of CVE-2022-23738 is medium, with a severity value of 5.7.
CVE-2022-23738 allows an unauthorized actor to access private repository files through a public repository on GitHub Enterprise Server.
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.
To fix CVE-2022-23738, it is recommended to upgrade GitHub Enterprise Server to a version that includes a fix for the vulnerability.