Incomplete cache verification issue in GitHub Enterprise Server leading to exposure of private repo files
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2022-23738
Credits & Attribution
The following person or organization is credited with identifying this vulnerability, as recorded in the NVD database:
- ahacker1
References
- https://docs.github.com/en/enterprise-server%403.2/admin/release-notes#3.2.20
- https://docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.15
- https://docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.10
- https://docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.7
- https://docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.3
More from GitHub
View All →Affected Vendor
GitHub
View all reports →