dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1374

CRITICAL · 9.1 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 3.8.15 / 3.9.10 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A 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 audit log forwarding. 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 confidence

Command injection vulnerability in GitHub Enterprise Server's Management Console allowing attackers with editor role to execute arbitrary commands via nomad templates when configuring audit log forwarding, potentially achieving admin SSH access to the appliance.

MitigationUpgrade to patched versions (3.11.5, 3.10.7, 3.9.10, or 3.8.15) or later. Additionally, restrict Management Console access and review editor role assignments to minimize insider threat surface.

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
Affected:< 3.8.15>= 3.9.0, < 3.9.10>= 3.10.0, < 3.10.7>= 3.11.0, < 3.11.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine GitHub Enterprise Server version
    Run the command `ghe-version` on the appliance shell or access the Management Console and check the dashboard for the version number
    Affected if The installed version is less than 3.8.15; or between 3.9.0 and 3.9.9 inclusive; or between 3.10.0 and 3.10.6 inclusive; or between 3.11.0 and 3.11.4 inclusive
  2. Verify audit log forwarding is configured
    Access the Management Console, navigate to the Audit log streaming or audit log forwarding settings, and check if any destination is configured
    Affected if Audit log forwarding is enabled and pointing to a remote destination
  3. Inspect nomad template usage in audit log settings
    In the Management Console audit log forwarding configuration, look for any custom nomad template fields or template syntax that may be used for log formatting
    Affected if Custom nomad templates are defined or template variables are being used in the audit log forwarding configuration
  4. Review Management Console user roles
    In the Management Console, go to User management and list accounts with the editor role, or query the internal user database via the enterprise admin API for users with editor permissions
    Affected if There are users assigned the editor role who have access to the Management Console

You are affected if your GitHub Enterprise Server version is vulnerable AND audit log forwarding is configured with nomad templates AND users with editor role have Management Console access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.8.15 / 3.9.10 / 3.10.7 or later
Fixed in 3.8.153.9.103.10.7
Interim mitigation

Upgrade to patched versions (3.11.5, 3.10.7, 3.9.10, or 3.8.15) or later. Additionally, restrict Management Console access and review editor role assignments to minimize insider threat surface.

Recommended fix High confidence

3.8.15, 3.9.10, 3.10.7, or 3.11.5 (depending on current release line)

  1. 1. Identify the current GitHub Enterprise Server version by navigating to the Management Console and checking the version information.
  2. 2. Determine which release line (3.8.x, 3.9.x, 3.10.x, or 3.11.x) the current installation is running.
  3. 3. For systems on version < 3.8.15: Upgrade to version 3.8.15 or later.
  4. 4. For systems on version >= 3.9.0 and < 3.9.10: Upgrade to version 3.9.10.
  5. 5. For systems on version >= 3.10.0 and < 3.10.7: Upgrade to version 3.10.7.
  6. 6. For systems on version >= 3.11.0 and < 3.11.5: Upgrade to version 3.11.5.
  7. 7. Review the GitHub Enterprise Server release notes for your target version to understand any required migration steps.
  8. 8. Perform a backup of the GitHub Enterprise Server instance before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1374 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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