Enterprise ServerApplication · GitHub
CVE-2024-1378
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 via nomad templates when configuring SMTP options. 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 allowed attackers with editor role privileges to inject arbitrary commands through nomad templates when configuring SMTP settings, potentially achieving admin SSH access to the appliance.
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.
-
Verify GitHub Enterprise Server versionAccess the Management Console and navigate to the About page, or run 'ghe-version' via SSH if administrative access is availableAffected if The installed version is < 3.8.15, or >= 3.9.0 and < 3.9.10, or >= 3.10.0 and < 3.10.7, or >= 3.11.0 and < 3.11.5
-
Identify users with editor role privilegesIn the Management Console, go to the Users and Teams settings and review the role assignments for each user accountAffected if Any user account is assigned the editor role, especially if untrusted or unexpected
-
Review SMTP configuration for unauthorized changesIn the Management Console, navigate to Email settings and examine the SMTP configuration history or audit logs for changes made by non-administrator accountsAffected if SMTP settings were modified by an editor role user or any untrusted account, or show unexpected values
-
Check Management Console access logsReview the Management Console audit logs for login events and configuration changes, particularly focusing on SMTP-related actionsAffected if There are log entries showing SMTP configuration changes from editor role users or from IP addresses not associated with known administrators
A user is affected if their GitHub Enterprise Server version falls within the vulnerable ranges AND an editor role user or attacker had access to configure SMTP settings in the Management Console.
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 patched, strictly limit Management Console access to trusted administrators only and monitor for unauthorized SMTP configuration changes.
Upgrade to version 3.8.15, 3.9.10, 3.10.7, or 3.11.5 depending on your current branch, or to version 3.12 or later
- 1. Identify the current GitHub Enterprise Server version by accessing the Management Console and checking the version information or running 'ghe-version' via SSH.
- 2. Determine the appropriate upgrade target based on your current version branch: if on 3.8.x upgrade to 3.8.15, if on 3.9.x upgrade to 3.9.10, if on 3.10.x upgrade to 3.10.7, if on 3.11.x upgrade to 3.11.5, or upgrade directly to 3.12 or later which is also unaffected.
- 3. Review the GitHub Enterprise Server upgrade prerequisites and ensure all backup requirements are met.
- 4. Create a complete backup of the GitHub Enterprise Server instance including database, git repositories, and configuration.
- 5. If available, test the upgrade in a staging environment matching production configuration.
- 6. Schedule a maintenance window as upgrades may require downtime.
- 7. Follow the official GitHub Enterprise Server upgrade procedure using the appropriate upgrade package for your target version.
- 8. After upgrade completes, verify the version via the Management Console or 'ghe-version' command.
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
- 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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1378 — 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-1378 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