Enterprise ServerApplication · GitHub
CVE-2024-2469
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 attacker with an Administrator role in GitHub Enterprise Server could gain SSH root access via remote code execution. This vulnerability affected GitHub Enterprise Server version 3.8.0 and above and was fixed in version 3.8.17, 3.9.12, 3.10.9, 3.11.7 and 3.12.1. 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 confidenceIn GitHub Enterprise Server versions 3.8.0 through the versions prior to the fixes, an authenticated attacker with Administrator privileges could execute arbitrary code remotely, which then allowed escalation to obtain SSH root access on the underlying system. This represents a complete compromise of the GHES instance.
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.17>= 3.9.0, < 3.9.12>= 3.10.0, < 3.10.9>= 3.11.0, < 3.11.7>= 3.12.0, < 3.12.1CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the installed GitHub Enterprise Server versionAccess the Management Console or use the admin shell with `ghe-version` command to retrieve the currently running GHES version.Affected if The installed version falls within any of these ranges: < 3.8.17, >= 3.9.0 and < 3.9.12, >= 3.10.0 and < 3.10.9, >= 3.11.0 and < 3.11.7, or >= 3.12.0 and < 3.12.1
-
Confirm administrative access to the instanceReview the list of Administrator accounts in the Management Console under 'Administering - Site admin settings' to identify accounts with administrative privileges.Affected if The instance has any Administrator accounts configured, particularly those not recognized or created by your organization.
-
Audit recent administrative actionsReview the audit log for Administrator activity. In the admin dashboard, navigate to the audit log and filter for events performed by site administrators, focusing on the timeframe since the instance was deployed or last audited.Affected if Unexpected administrative actions appear in the logs, such as unfamiliar user modifications, settings changes, or code execution events that were not initiated by authorized personnel.
-
Check for unauthorized SSH accessReview SSH access logs on the GHES appliance for any root-level SSH sessions. Use the admin shell to examine `/var/log/auth.log` or run `ghe-ssh-check` if available for signs of unexpected root logins.Affected if SSH sessions to root or unusual IP addresses appear in the system logs, indicating potential escalation to underlying system access.
The environment is affected if GitHub Enterprise Server is running a version prior to 3.8.17, 3.9.12, 3.10.9, 3.11.7, or 3.12.1 and the instance has Administrator accounts that may have been compromised or used for unauthorized actions.
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.173.9.123.10.9
Upgrade GitHub Enterprise Server to version 3.8.17, 3.9.12, 3.10.9, 3.11.7, or 3.12.1 or later. Additionally, audit Administrator accounts and review access logs for unauthorized administrative actions.
3.12.1 (or the minimum fixed version for your current release branch: 3.8.17, 3.9.12, 3.10.9, or 3.11.7)
- Identify the current GitHub Enterprise Server version from the Management Console or admin shell
- Determine the appropriate upgrade path based on current version: if < 3.8.17 upgrade to 3.8.17 or later; if >= 3.9.0 and < 3.9.12 upgrade to 3.9.12 or later; if >= 3.10.0 and < 3.10.9 upgrade to 3.10.9 or later; if >= 3.11.0 and < 3.11.7 upgrade to 3.11.7 or later
- Review GitHub Enterprise Server upgrade prerequisites and backup procedures in official documentation
- Schedule a maintenance window appropriate for the upgrade
- Follow the standard GitHub Enterprise Server upgrade procedure using the GitHub virtual appliance or hotpatch method
- Verify the upgrade completed successfully and the new version is reflected in the Management Console
- Confirm the vulnerability is resolved by verifying the version is at or above the fixed release for your upgrade track
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2469 — 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-2469 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