Enterprise ServerApplication · GitHub
CVE-2024-1372
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 SAML 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.12 and was fixed in versions 3.11.5, 3.10.7, 3.9.10, and 3.8.15. This vulnerability was reported via the GitHub Bug Bounty program https://bounty.github.com .
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 in GitHub Enterprise Server's Management Console SAML settings allowed an attacker with only editor role permissions to execute arbitrary commands and gain admin SSH access to the appliance. The attacker could inject OS commands through crafted SAML configuration parameters.
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.15>= 3.9.0, < 3.9.10>= 3.10.0, < 3.10.7>= 3.11.0, < 3.11.5CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 versionAccess the Management Console and navigate to the 'About' page, or run 'ghe-version' via SSH on the appliance. Alternatively, check the site admin dashboard footer which displays the version.Affected if The installed version falls into any of these ranges: < 3.8.15, >= 3.9.0 and < 3.9.10, >= 3.10.0 and < 3.10.7, or >= 3.11.0 and < 3.11.5
-
Confirm Management Console SAML authentication is configuredIn the Management Console, go to 'Authentication' > 'SAML' and verify if SAML is enabled. The vulnerability is only exploitable when SAML is configured as the authentication provider.Affected if SAML authentication is enabled and the version is in the affected range listed above
-
Audit user accounts with editor role permissionsIn the Management Console, navigate to 'Users' or 'Site administrators' and review accounts marked with 'editor' role. The vulnerability allows editors to inject commands.Affected if Any user account possesses editor role permissions and the above conditions are met
-
Review SAML configuration for unexpected parametersIn the Management Console under 'Authentication' > 'SAML', inspect all SAML fields (IdP entity ID, SSO URL, certificate, attribute mappings) for any suspicious or unexpected values that could indicate prior exploitation.Affected if SAML configuration contains unexpected attribute values and the version is affected
A user is affected if their GitHub Enterprise Server version is in the vulnerable range AND SAML authentication is enabled in the Management Console, allowing any user with editor role to potentially execute commands.
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.153.9.103.10.7
Upgrade GitHub Enterprise Server to version 3.11.5, 3.10.7, 3.9.10, 3.8.15 or later. Until upgrade is possible, strictly limit Management Console access to trusted administrators only and audit existing editor accounts.
Upgrade to GitHub Enterprise Server 3.12 or later (or at minimum the version appropriate to your branch: 3.8.15, 3.9.10, 3.10.7, or 3.11.5)
- 1. Schedule a maintenance window and create a full backup of the GitHub Enterprise Server instance
- 2. Download the appropriate upgrade package for your current version from GitHub Enterprise downloads
- 3. For versions 3.8.x: upgrade to 3.8.15 or later (recommended: upgrade to 3.12+)
- 4. For versions 3.9.x: upgrade to 3.9.10 or later (recommended: upgrade to 3.12+)
- 5. For versions 3.10.x: upgrade to 3.10.7 or later (recommended: upgrade to 3.12+)
- 6. For versions 3.11.x: upgrade to 3.11.5 or later (recommended: upgrade to 3.12+)
- 7. Run the upgrade using the GitHub Enterprise Server upgrade procedures
- 8. After upgrade, verify the Management Console is accessible and review SAML configuration settings
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
- 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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1372 — 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-1372 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