Enterprise ServerApplication · GitHub
CVE-2024-0200
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 · uneditedAn unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. This vulnerability could lead to the execution of user-controlled methods and remote code execution. To exploit this bug, an actor would need to be logged into an account on the GHES instance with the organization owner role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.8.13, 3.9.8, 3.10.5, and 3.11.3. 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 confidenceAn unsafe reflection vulnerability in GitHub Enterprise Server allows reflection injection where user-controlled input determines which methods are executed via Java reflection APIs. This enables remote code execution. Exploitation requires an authenticated session with organization owner privileges.
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.8.0, < 3.8.13>= 3.9.0, < 3.9.8>= 3.10.0, < 3.10.5>= 3.11.0, < 3.11.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check GitHub Enterprise Server versionRun 'ghe-version' command in the GitHub Enterprise admin shell, or check the Management Console dashboard under the 'About' sectionAffected if The installed version falls within any of these ranges: 3.8.0-3.8.12, 3.9.0-3.9.7, 3.10.0-3.10.4, or 3.11.0-3.11.2
-
Verify admin user privilegesIn the GitHub Enterprise admin console, navigate to the organization settings and review the list of organization owners under the 'People' sectionAffected if There are untrusted or compromised accounts granted organization owner role that could exploit the reflection vulnerability
-
Review audit logs for reflection API activityIn the GitHub Enterprise admin settings, access the audit log and search for unusual API calls or method invocations that may indicate reflection injection attemptsAffected if Audit logs show suspicious API activity or unexpected method executions that could represent exploitation attempts
-
Check for unauthorized changes to organization settingsReview the organization audit log for any unauthorized modifications to organization configuration, webhooks, or team memberships made by organization ownersAffected if Changes were made by organization owners that were not authorized or expected, potentially as part of exploitation
You are affected if your GitHub Enterprise Server version is 3.8.x before 3.8.13, 3.9.x before 3.9.8, 3.10.x before 3.10.5, or 3.11.x before 3.11.3, and you have organization owner accounts that could be compromised.
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.8.133.9.83.10.5
Upgrade GitHub Enterprise Server to version 3.8.13, 3.9.8, 3.10.5, 3.11.3, or 3.12+. If upgrading is not immediately feasible, restrict organization owner permissions to only trusted administrators and monitor for suspicious activity.
Upgrade to 3.8.13, 3.9.8, 3.10.5, 3.11.3, or preferably 3.12+ (latest stable release)
- 1. Back up your GitHub Enterprise Server data and configuration
- 2. Schedule a maintenance window as upgrades may require downtime
- 3. Identify your current version using the Management Console or administrative shell
- 4. For version 3.8.x: upgrade to version 3.8.13 or later
- 5. For version 3.9.x: upgrade to version 3.9.8 or later
- 6. For version 3.10.x: upgrade to version 3.10.5 or later
- 7. For version 3.11.x: upgrade to version 3.11.3 or later
- 8. Alternatively, upgrade to version 3.12 or later which includes all fixes
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
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0200 — 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-0200 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