dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1354

HIGH · 8.0 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 →
86/100
Remediation priority · High
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 the `syslog-ng` configuration file. 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.

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 syslog-ng configuration allows an attacker with editor role to inject arbitrary commands via the configuration file and gain admin SSH access to the appliance. This is a privilege escalation combined with command injection.

MitigationApply the patched versions (3.11.5, 3.10.7, 3.9.10, or 3.8.15) and review Management Console access to ensure only trusted personnel have editor roles.

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify GitHub Enterprise Server version
    Access the Management Console or run 'ghe-version' via SSH on the appliance. The version is also displayed on the login page footer of the Management Console.
    Affected if The installed version falls within any of these ranges: < 3.8.15; >= 3.9.0 and < 3.9.10; >= 3.10.0 and < 3.10.7; >= 3.11.0 and < 3.11.5
  2. Confirm Management Console is accessible
    Navigate to the Management Console at https://hostname:8443/_global_system/ or access via SSH and run 'ghe-manage'.
    Affected if The Management Console is reachable and exposed (especially to untrusted networks).
  3. Review Management Console user roles
    In the Management Console, go to Settings > Site admin settings > Authentication > Management Console users, or list users via the admin SSH command 'ghe-api /admin/users' to check for users with 'editor' role.
    Affected if There are user accounts assigned the 'editor' role in the Management Console, particularly users who are not fully trusted.
  4. Check if syslog-ng configuration is in use
    In the Management Console, navigate to Logging > Syslog (syslog-ng) settings to see if syslog-ng export is configured and enabled.
    Affected if Syslog-ng logging is enabled and configured, allowing the vulnerable configuration file to be modified.

You are affected if your GitHub Enterprise Server version is in the vulnerable ranges AND the Management Console is accessible to users with editor role AND syslog-ng configuration is enabled.

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

Apply the patched versions (3.11.5, 3.10.7, 3.9.10, or 3.8.15) and review Management Console access to ensure only trusted personnel have editor roles.

Recommended fix High confidence

3.12.0 or later (minimum: 3.8.15, 3.9.10, 3.10.7, or 3.11.5 depending on your release line)

  1. Identify the current GitHub Enterprise Server version by checking the Management Console or using the GitHub Enterprise API
  2. Determine which upgrade path applies based on current version (3.8.x -> 3.8.15+, 3.9.x -> 3.9.10+, 3.10.x -> 3.10.7+, or 3.11.x -> 3.11.5+)
  3. Review the GitHub Enterprise Server upgrade documentation for your specific version path
  4. Create a complete backup of the GitHub Enterprise Server instance, including configuration and data
  5. Schedule a maintenance window as upgrades require downtime
  6. Follow the documented upgrade procedure for your GitHub Enterprise Server version
  7. After upgrade, verify the Management Console is accessible and the version matches the expected fixed release
  8. Confirm the syslog-ng configuration is functioning correctly
Caveat Standard GitHub Enterprise Server upgrade precautions apply - review release notes for your version path for any known issues or migration requirements

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1354 — 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-1354 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