dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-10007

CRITICAL · 9.1 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to 3.11.17 / 3.12.11 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 path collision and arbitrary code execution vulnerability was identified in GitHub Enterprise Server that allowed container escape to escalate to root via ghe-firejail path. Exploitation of this vulnerability requires Enterprise Administrator access to the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise prior to 3.15 and was fixed in versions 3.14.3, 3.13.6, 3.12.11, and 3.11.17. 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 path collision vulnerability in GitHub Enterprise Server's ghe-firejail sandbox allows Enterprise Administrators to escape container isolation and escalate to root privileges on the host system. This is a local privilege escalation from a privileged container to host root.

MitigationUpgrade GitHub Enterprise Server to version 3.14.3, 3.13.6, 3.12.11, or 3.11.17 or later to patch this vulnerability. Restrict Enterprise Administrator access and monitor for suspicious admin activity.

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.11.17>= 3.12.0, < 3.12.11>= 3.13.0, < 3.13.6>= 3.14.0, < 3.14.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
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 GitHub Enterprise Server version
    Run 'ghe-version' command on the GitHub Enterprise Server appliance, or check the Management Console dashboard under 'Version' information
    Affected if The installed version falls into any of these ranges: < 3.11.17, >= 3.12.0 and < 3.12.11, >= 3.13.0 and < 3.13.6, or >= 3.14.0 and < 3.14.3
  2. Confirm Enterprise Administrator privileges exist
    Check if any user account has Enterprise Administrator role by navigating to Site Admin > Enterprise > Settings, or by querying the administrative user list via 'ghe-api /enterprise/settings'
    Affected if There exists at least one Enterprise Administrator account, as this is a required condition for exploiting the vulnerability
  3. Verify ghe-firejail binary is present
    Check for the existence of the ghe-firejail binary on the system by running 'ls -la /usr/local/bin/ghe-firejail' or using 'which ghe-firejail'
    Affected if The ghe-firejail binary exists and is executable, as the path collision vulnerability exploits this specific component

The environment is affected if the installed GitHub Enterprise Server version is vulnerable AND an Enterprise Administrator account exists AND the ghe-firejail binary is present on the system.

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.11.17 / 3.12.11 / 3.13.6 or later
Fixed in 3.11.173.12.113.13.6
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.14.3, 3.13.6, 3.12.11, or 3.11.17 or later to patch this vulnerability. Restrict Enterprise Administrator access and monitor for suspicious admin activity.

Recommended fix High confidence

Upgrade to version 3.14.3, 3.13.6, 3.12.11, or 3.11.17 (matching your current branch), or preferably to version 3.15.0 or later

  1. 1. Back up your GitHub Enterprise Server instance data and configuration before starting the upgrade.
  2. 2. Download the appropriate fixed version for your current release branch: 3.14.3 (for 3.14.x), 3.13.6 (for 3.13.x), 3.12.11 (for 3.12.x), or 3.11.17 (for 3.11.x).
  3. 3. Alternatively, upgrade directly to version 3.15.0 or later, which is not affected by this vulnerability.
  4. 4. Follow the official GitHub Enterprise Server upgrade documentation to apply the update package.
  5. 5. After upgrade completion, verify the ghe-firejail binary permissions and version to confirm the patch was applied.
  6. 6. Test that Enterprise Administrator functions work correctly after the upgrade.
Caveat Standard GitHub Enterprise Server upgrade considerations apply - review release notes for your target version for any configuration 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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