CVE-2024-6395 GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Deploy Keys
Attackers can enumerate private repository names using deploy keys, exposing sensitive metadata without accessing content.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-6395?
CVE-2024-6395 is a medium-severity vulnerability in Github Enterprise Server, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An exposure of sensitive information vulnerability in GitHub Enterprise Server would allow an attacker to enumerate the names of private repositories that utilize deploy keys. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17. This vulnerability was reported via the GitHub Bug Bounty program.
Weakness: CWE-200
Which versions are affected by CVE-2024-6395?
It affects 1 product.
Products include Github Enterprise Server.
How do I fix CVE-2024-6395?
No fix has been published for CVE-2024-6395 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-6395 being exploited?
There is no known exploitation of CVE-2024-6395 in the wild and no public exploit code.
Other vulnerabilities in Github Enterprise Server
- CVE-2024-4985 Auth bypass in Enterprise Server
- CVE-2022-23739 Missing authorization in GitHub Enterprise Server
- CVE-2022-46255 Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE
- CVE-2021-22869 Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group
- CVE-2024-9487 Auth bypass in Enterprise Server
Sources
Also known as GHSA-p46f-3938-pv7g.