CVE-2024-6395: GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Deploy Keys

Published Jul 16, 2024
·
Updated

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.

Affected Software

5 affected components
github Enterprise Server>=3.9.0<3.9.17
github Enterprise Server>=3.10.0<3.10.14
github Enterprise Server>=3.11.0<3.11.12
github Enterprise Server>=3.12.0<3.12.6
github Enterprise Server=3.13.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.14
  2. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.13.1
  3. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.12.6
  4. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.11.12
  5. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.10.14
  6. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.9.17

Event History

Jul 16, 2024
CVE Published
via MITRE·09:27 PM
Data Sourced
via MITRE·09:27 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-6395?

CVE-2024-6395 is classified as a vulnerability that allows information exposure but does not compromise repository content.

2

How do I fix CVE-2024-6395?

To mitigate CVE-2024-6395, upgrade your GitHub Enterprise Server to version 3.10.15 or later, or to the latest version available.

3

Which versions of GitHub Enterprise Server are affected by CVE-2024-6395?

CVE-2024-6395 affects GitHub Enterprise Server versions from 3.9.0 to 3.9.17, from 3.10.0 to 3.10.14, from 3.11.0 to 3.11.12, from 3.12.0 to 3.12.6, and the exact version 3.13.0.

4

What type of information can be leaked due to CVE-2024-6395?

CVE-2024-6395 allows an attacker to enumerate the names of private repositories utilizing deploy keys.

5

Does CVE-2024-6395 allow unauthorized access to repository contents?

No, CVE-2024-6395 only exposes the repository names and does not allow access to the actual content.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203