Enterprise ServerApplication · GitHub
CVE-2024-2443
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 command injection vulnerability was identified in GitHub Enterprise Server that allowed an attacker with an editor role in the Management Console to gain admin SSH access to the appliance when configuring GeoJSON settings. Exploitation of this vulnerability required access to the GitHub Enterprise Server instance and access to the Management Console with the editor role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.13 and was fixed in versions 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 confidenceA command injection vulnerability existed in GitHub Enterprise Server's Management Console GeoJSON settings. An attacker with editor role privileges could inject arbitrary commands through GeoJSON configuration, achieving admin SSH access to the appliance. This represents a privilege escalation from editor to full admin shell access.
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 installed GitHub Enterprise Server versionRun 'ghe-version' command on the appliance or access the Management Console footer which displays the version numberAffected if The version falls within 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 Management Console is accessibleAccess the Management Console at /setup/ or check if port 8443 is open and responding on the applianceAffected if The Management Console is reachable and exposed (the vulnerability requires interaction with the GeoJSON settings within it)
-
Verify GeoJSON feature exists in Management ConsoleLog into Management Console and navigate to the GeoJSON configuration settings under the relevant settings sectionAffected if The GeoJSON configuration interface is present and available for editing (this is the attack surface for the vulnerability)
-
Check for editor role usersReview user accounts in the Management Console under Site Admin > Users or check for users with editor-level permissions on the applianceAffected if There are users with editor role privileges (an attacker with editor role is required to exploit this vulnerability)
You are affected if your GitHub Enterprise Server version is within the affected ranges AND the Management Console is accessible AND users with editor role exist, allowing privilege escalation to admin SSH access.
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, 3.12.1, or 3.13 and later. Until upgraded, restrict Management Console access to only fully trusted administrators and consider network isolation of the appliance.
Upgrade to 3.12.1 or later (or the appropriate minor version fix: 3.8.17, 3.9.12, 3.10.9, or 3.11.7)
- 1. Back up your GitHub Enterprise Server instance before attempting any upgrade
- 2. Identify your current version from the Administrative Center (/settings)
- 3. Based on your current version, determine the appropriate upgrade path: if < 3.8.17 upgrade to 3.8.17+; if >= 3.9.0 and < 3.9.12 upgrade to 3.9.12+; if >= 3.10.0 and < 3.10.9 upgrade to 3.10.9+; if >= 3.11.0 and < 3.11.7 upgrade to 3.11.7+
- 4. Download the appropriate upgrade package from github.com/enterprise
- 5. Follow the official GitHub Enterprise Server upgrade procedure in the administration guide
- 6. After upgrade, verify the version in the Management Console confirms the fix is applied
- 7. Review Management Console GeoJSON settings to ensure no unauthorized configurations were added
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 / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2443 — 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-2443 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