CVE-2024-6395

GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Deploy Keys

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.

Category

6.3
CVSS
Severity: Medium
CVSS 4.0 •
CVSS 3.1 •
EPSS 0.15%
Affected: GitHub GitHub Enterprise Server
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2024-6395?
CVE-2024-6395 has been scored as a medium severity vulnerability.
How to fix CVE-2024-6395?
To fix CVE-2024-6395, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-6395 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-6395 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-6395?
CVE-2024-6395 affects GitHub GitHub Enterprise Server.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.