dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-6395

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 3.9.17 / 3.10.14 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitHub Enterprise Server prior to version 3.14 contains an information disclosure vulnerability where an attacker can enumerate the names of private repositories that utilize deploy keys. This is achieved through the API or web interface revealing repository names that should remain confidential. No actual repository content or code is accessible—only the names are exposed.

MitigationUpgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17 or later. If immediate patching is not possible, monitor API access logs for unusual patterns of repository name enumeration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise ServerApplication
Affected:>= 3.9.0, < 3.9.17>= 3.10.0, < 3.10.14>= 3.11.0, < 3.11.12>= 3.12.0, < 3.12.6= 3.13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitHub Enterprise Server version
    Access the GitHub Enterprise Server admin console or check via the management console. The version is typically displayed on the dashboard or in the /setup/settings page.
    Affected if The installed version is 3.9.0 through 3.9.16, 3.10.0 through 3.10.13, 3.11.0 through 3.11.11, 3.12.0 through 3.12.5, or exactly 3.13.0.
  2. Determine if private repositories use deploy keys
    Review the organization's repository settings via the web interface or API to identify repositories that have deploy keys configured. Deploy keys are listed under each repository's Settings > Deploy keys section.
    Affected if Private repositories with deploy keys are configured on the instance.
  3. Test API repository name disclosure
    Use an authenticated API request with a deploy key to access the repository endpoint. For example, query the GitHub API using the deploy key credentials and observe if private repository names that should not be visible are returned in API responses.
    Affected if Private repository names that you do not own or have access to become visible through API responses when using deploy key authentication.
  4. Test web interface repository name disclosure
    Log in with an account that has only deploy key access. Navigate through the web interface and observe whether private repository names that should be confidential are displayed in repository lists, dropdowns, or search results.
    Affected if Private repository names are displayed in the web interface to users who should not have visibility into those repository names.

You are affected if your GitHub Enterprise Server version falls within the vulnerable ranges AND private repository names become visible through the API or web interface to users who only possess deploy key authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.9.17 / 3.10.14 / 3.11.12 or later
Fixed in 3.9.173.10.143.11.12
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17 or later. If immediate patching is not possible, monitor API access logs for unusual patterns of repository name enumeration.

Recommended fix High confidence

Upgrade to 3.9.17, 3.10.14, 3.11.12, 3.12.6, or 3.13.1 (or the latest 3.13.x/3.14.x release) depending on your current major version branch

  1. Back up your GitHub Enterprise Server data and configuration before starting the upgrade
  2. Access the GitHub Enterprise Server management console or use the administrative SSH console
  3. Follow the standard upgrade procedure for your current version path: for 3.9.x upgrade to 3.9.17, for 3.10.x upgrade to 3.10.14, for 3.11.x upgrade to 3.11.12, for 3.12.x upgrade to 3.12.6, or for 3.13.x upgrade to 3.13.1
  4. Apply the upgrade package appropriate for your infrastructure
  5. Verify the upgrade completed successfully by checking the management console status page
  6. Confirm the sensitive repository name enumeration issue is resolved by testing that repository names via deploy keys are no longer exposed
Caveat Standard GitHub Enterprise Server upgrade considerations apply including maintenance window requirements and potential rollback planning; no specific breaking changes documented for this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6395 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data