dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1355

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 the actions-console docker container while setting a service URL. 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

A command injection vulnerability in GitHub Enterprise Server's Management Console allows attackers with editor role to execute arbitrary commands via the actions-console docker container when setting a service URL, potentially achieving admin SSH access to the appliance.

MitigationUpgrade to GitHub Enterprise Server versions 3.11.5, 3.10.7, 3.9.10, 3.8.15 or later. If immediate patching is not possible, restrict Management Console access to trusted administrators only and audit existing editor-role accounts.

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. Identify installed GitHub Enterprise Server version
    Access the Management Console and navigate to the 'About' page, or run `ghe-version` via SSH if you have admin access to the appliance
    Affected if The installed version falls within these vulnerable ranges: < 3.8.15, >= 3.9.0 but < 3.9.10, >= 3.10.0 but < 3.10.7, or >= 3.11.0 but < 3.11.5
  2. Verify Management Console access controls
    Review the Management Console authentication settings and network access controls to determine if editor-role accounts could be accessed by untrusted users
    Affected if The Management Console is accessible to users with editor role who are not fully trusted administrators
  3. Enumerate editor-role accounts
    In the Management Console, go to 'Users' or 'Access management' and list all accounts assigned the editor role
    Affected if There are editor-role accounts that were not explicitly created by trusted administrators
  4. Inspect actions-console service URL configuration
    In the Management Console, navigate to the Actions settings or Docker container service URL configuration panel and examine the current service URL value for the actions-console container
    Affected if The actions-console docker container service URL contains unexpected characters, multiple URLs, or payloads that were not explicitly set by administrators

A user is affected if their GitHub Enterprise Server version is within the vulnerable ranges listed AND they have untrusted accounts with editor role who can access the Management Console actions-console service URL configuration.

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 GitHub Enterprise Server versions 3.11.5, 3.10.7, 3.9.10, 3.8.15 or later. If immediate patching is not possible, restrict Management Console access to trusted administrators only and audit existing editor-role accounts.

Recommended fix High confidence

3.11.5 (or the latest 3.x release >= your current branch's fixed version)

  1. 1. Identify the current GitHub Enterprise Server version running in your environment
  2. 2. Based on your current version branch, upgrade to the corresponding fixed version: 3.8.15, 3.9.10, 3.10.7, or 3.11.5
  3. 3. If possible, upgrade to the latest stable release (3.11.5 or later if available) to get all security fixes
  4. 4. After upgrade, verify that the Management Console is accessible and functioning normally
  5. 5. Review Management Console settings, particularly the actions-console service URL configuration, to ensure no unauthorized changes were made

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
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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