dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-2440

MEDIUM · 5.9 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 3.9.13 / 3.10.10 or later.
See remediation →
65/100
Remediation priority · Elevated
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 race condition in GitHub Enterprise Server allowed an existing admin to maintain permissions on a detached repository by making a GraphQL mutation to alter repository permissions while the repository is detached. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.13 and was fixed in versions 3.9.13, 3.10.10, 3.11.8 and 3.12.1. 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 race condition in GitHub Enterprise Server's GraphQL API allowed an authenticated administrator to maintain permissions on a repository after it was detached from its original organization. By timing a GraphQL mutation to alter repository permissions during the detachment process, an admin could retain unauthorized access to the detached repository.

MitigationUpgrade GitHub Enterprise Server to version 3.9.13, 3.10.10, 3.11.8, 3.12.1, or 3.13 or later. Alternatively, audit admin accounts and repository permissions to identify any unexpected permission persistence on detached repositories.

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.9.13>= 3.10.0, < 3.10.10>= 3.11.0, < 3.11.8>= 3.12.0, < 3.12.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

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. Check GitHub Enterprise Server version
    Run 'ghe-version' from the management shell or check the GitHub Enterprise Admin settings page to determine the exact version number
    Affected if The installed version falls within any of these ranges: < 3.9.13, >= 3.10.0 and < 3.10.10, >= 3.11.0 and < 3.11.8, or >= 3.12.0 and < 3.12.1
  2. Identify repositories detached from organizations
    Use the GraphQL API or admin site to query for repositories that are not owned by any organization, or review recent repository detachment events in the audit log
    Affected if Any repository has been detached from an organization and the GHES version is vulnerable
  3. Review admin permissions on detached repositories
    Query the repository permissions via GraphQL or check each detached repository's settings page to list all users and teams with access, focusing on admin-level permissions
    Affected if Any administrator account retains permissions on a repository after it was detached from its original organization, especially if that admin was not the owner of the original organization
  4. Audit admin accounts for unauthorized access
    Compare the list of admin accounts in the system against expected admin users. Cross-reference with admin access found on detached repositories in the previous step
    Affected if There are administrators who have permissions to repositories they should not have access to after those repositories were detached

You are affected if your GitHub Enterprise Server version is in the vulnerable range and you have repositories that were detached from organizations with unexpected admin permissions persisting.

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.9.13 / 3.10.10 / 3.11.8 or later
Fixed in 3.9.133.10.103.11.8
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.9.13, 3.10.10, 3.11.8, 3.12.1, or 3.13 or later. Alternatively, audit admin accounts and repository permissions to identify any unexpected permission persistence on detached repositories.

Recommended fix High confidence

3.12.1 (or latest stable 3.x release)

  1. Schedule a maintenance window for the GitHub Enterprise Server upgrade
  2. Back up your GitHub Enterprise Server instance data and configuration
  3. Test the upgrade in a staging environment before applying to production
  4. Upgrade to version 3.9.13, 3.10.10, 3.11.8, or 3.12.1 (or a later version if available)
  5. Verify the upgrade was successful by checking the administrative UI and testing repository permission functionality
Caveat Review GitHub Enterprise Server release notes for any migration requirements between your current version and target version

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-2440 — 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-2440 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