dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-0507

HIGH · 8.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 3.8.13 / 3.9.8 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS 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
An attacker with access to a Management Console user account with the editor role could escalate privileges through a command injection vulnerability in the Management Console. This vulnerability affected all versions of GitHub Enterprise Server and was fixed in versions 3.11.3, 3.10.5, 3.9.8, and 3.8.13 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 exists in the GitHub Enterprise Server Management Console that allows authenticated users with editor role to execute arbitrary commands, leading to privilege escalation. This affects all versions prior to the patched releases 3.11.3, 3.10.5, 3.9.8, and 3.8.13.

MitigationUpgrade GitHub Enterprise Server to version 3.11.3, 3.10.5, 3.9.8, or 3.8.13 or later. Additionally, review and restrict Management Console access, ensuring only necessary 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.13>= 3.9.0, < 3.9.8>= 3.10.0, < 3.10.5>= 3.11.0, < 3.11.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 admin panel and view the 'Version' information in the footer, or run `ghe-version` from the administrative SSH shell
    Affected if The installed version is before 3.8.13, between 3.9.0-3.9.7, between 3.10.0-3.10.4, or between 3.11.0-3.11.2
  2. Confirm Management Console is accessible
    Attempt to access the Management Console at your-GHE-hostname:8443/manage or /__developer__/router in a web browser and verify the login page loads
    Affected if The Management Console interface is reachable and accepts authentication
  3. Audit Management Console user roles
    Log into the Management Console as an administrator, navigate to 'Users' or 'Access' settings, and review which users are assigned the 'editor' role
    Affected if Any user account has been granted the editor role in the Management Console (this role is required for the exploit to work)

You are affected if your GitHub Enterprise Server version falls within the vulnerable ranges AND the Management Console is accessible with users having editor roles.

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.13 / 3.9.8 / 3.10.5 or later
Fixed in 3.8.133.9.83.10.5
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.11.3, 3.10.5, 3.9.8, or 3.8.13 or later. Additionally, review and restrict Management Console access, ensuring only necessary personnel have editor roles.

Recommended fix High confidence

3.8.13, 3.9.8, 3.10.5, or 3.11.3 (depending on current major version branch)

  1. Identify the currently installed GitHub Enterprise Server version using the Management Console or administrative commands
  2. Plan maintenance window as upgrades require downtime
  3. Back up GitHub Enterprise Server data and configuration according to standard backup procedures
  4. For versions < 3.8.13: Upgrade directly to version 3.8.13 or later within the 3.8.x line
  5. For versions >= 3.9.0 and < 3.9.8: Upgrade to version 3.9.8 or later within the 3.9.x line
  6. For versions >= 3.10.0 and < 3.10.5: Upgrade to version 3.10.5 or later within the 3.10.x line
  7. For versions >= 3.11.0 and < 3.11.3: Upgrade to version 3.11.3 or later within the 3.11.x line
  8. Execute upgrade following official GitHub Enterprise Server upgrade documentation
Caveat Standard GitHub Enterprise Server upgrade considerations apply including downtime and potential migration requirements; review release notes for specific version transitions

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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