Enterprise ServerApplication · GitHub
CVE-2024-8810
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 · uneditedA GitHub App installed in organizations could upgrade some permissions from read to write access without approval from an organization administrator. An attacker would require an account with administrator access to install a malicious GitHub App. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.14.1, 3.13.4, 3.12.9, 3.11.15, and 3.10.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 confidenceA vulnerability in GitHub Enterprise Server allowed malicious GitHub Apps to elevate permissions from read to write access without organization administrator approval. An attacker with administrator privileges could install a crafted GitHub App that silently upgrades its own permissions.
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
>= 3.10.0, < 3.10.17>= 3.11.0, < 3.11.15>= 3.12.0, < 3.12.9>= 3.13.0, < 3.13.4= 3.14.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionLog into the GitHub Enterprise Server Management Console and navigate to the 'About' page, or use the administrative shell command `ghe-version` to retrieve the installed version number.Affected if The displayed version falls within any of these vulnerable ranges: 3.10.0 to 3.10.16, 3.11.0 to 3.11.14, 3.12.0 to 3.12.8, 3.13.0 to 3.13.3, or exactly 3.14.0.
-
Review organization-installed GitHub AppsAs an organization administrator, go to Organization Settings > GitHub Apps and enumerate all installed GitHub Apps. Check each app's permission grants, specifically looking for any apps with write permissions that were originally granted only read access.Affected if Any GitHub App in the organization has elevated from read-only to write permissions without a documented administrator approval action.
-
Audit GitHub App installation eventsNavigate to the organization's audit log and search for events containing 'GitHub App' and 'permission' to identify any permission modification events. Look for timestamps corresponding to the period when the vulnerable version was in use.Affected if Audit log shows GitHub App permission changes that were not initiated by an explicit administrator action through the normal approval workflow.
You are affected if your GitHub Enterprise Server version is 3.10.0-3.10.16, 3.11.0-3.11.14, 3.12.0-3.12.8, 3.13.0-3.13.3, or exactly 3.14.0, or if unauthorized permission escalation events appear in your organization audit logs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.173.11.153.12.9
Upgrade GitHub Enterprise Server to version 3.14.1, 3.13.4, 3.12.9, 3.11.15, or 3.10.17 or later. Review and audit all installed GitHub Apps in affected organizations for unauthorized permission escalations.
3.10.17, 3.11.15, 3.12.9, 3.13.4, or 3.14.1 (depending on current branch)
- 1. Identify the current GitHub Enterprise Server version by navigating to the Management Console or running 'ghe-version' via SSH
- 2. Determine which version branch you are currently running (3.10.x, 3.11.x, 3.12.x, or 3.13.x)
- 3. For 3.10.x branch: upgrade to version 3.10.17
- 4. For 3.11.x branch: upgrade to version 3.11.15
- 5. For 3.12.x branch: upgrade to version 3.12.9
- 6. For 3.13.x branch: upgrade to version 3.13.4
- 7. Alternatively, upgrade to version 3.14.1 which contains all security fixes
- 8. Review release notes and perform upgrade during a planned maintenance window following standard GitHub Enterprise Server upgrade procedures
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
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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