dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-5817

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed read access to issue content via GitHub Projects. This was only exploitable in internal repositories and required the attacker to have access to the corresponding project board. 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

An Incorrect Authorization vulnerability in GitHub Enterprise Server allowed read access to issue content in internal repositories via GitHub Projects. An attacker with project board access could bypass normal repository authorization controls to view issues they shouldn't have permission to access.

MitigationUpgrade GitHub Enterprise Server to version 3.14 or later, or to one of the patched versions (3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17).

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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
    Run 'ghe-version' command in the management shell or check the /etc/github/build file, or navigate to the Management Console > About page
    Affected if The installed version is 3.9.0-3.9.16, 3.10.0-3.10.13, 3.11.0-3.11.11, 3.12.0-3.12.5, or 3.13.0 exactly
  2. Verify GitHub Projects is in use
    Check if any project boards exist by querying the API: 'gh api projects --hostname <enterprise_host>' or via the web UI at /organizations/<org>/projects
    Affected if Project boards are created and contain internal repositories
  3. Confirm internal repository presence
    List repositories with visibility set to internal: 'gh api repos --hostname <enterprise_host> --jq '.[] | select(.visibility == "internal") | .name''
    Affected if Internal repositories exist in the enterprise organization
  4. Test authorization boundary
    Create a test user without access to an internal repository, add them to a project board that contains that internal repository, then attempt to view issues via the project board UI or API
    Affected if The user can view issue content from the internal repository despite lacking direct repository access

A user is affected if running a GitHub Enterprise Server version in the affected ranges AND using GitHub Projects with internal repositories where unauthorized users have project board access.

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.14 or later, or to one of the patched versions (3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17).

Recommended fix High confidence

Upgrade to 3.9.17, 3.10.14, 3.11.12, 3.12.6, or preferably 3.13.1 or later

  1. 1. Identify the current GitHub Enterprise Server version by navigating to the Administration dashboard or running 'ghe-version' from the management shell.
  2. 2. Determine which version branch your current installation is on (3.9.x, 3.10.x, 3.11.x, or 3.12.x).
  3. 3. If on 3.9.x branch, upgrade to version 3.9.17 or later.
  4. 4. If on 3.10.x branch, upgrade to version 3.10.14 or later.
  5. 5. If on 3.11.x branch, upgrade to version 3.11.12 or later.
  6. 6. If on 3.12.x branch, upgrade to version 3.12.6 or later.
  7. 7. Alternatively, upgrade to version 3.13.1 or later (the latest stable release) to receive all security patches.
  8. 8. After upgrade, verify that internal repository issue content is no longer accessible via GitHub Projects without proper authorization.

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5817 — 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-5817 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