dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-5566

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 3.9.17 / 3.10.14 or later.
See remediation →
71/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
An improper privilege management vulnerability allowed users to migrate private repositories without having appropriate scopes defined on the related Personal Access Token. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in version 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17.

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

An improper privilege management vulnerability in GitHub Enterprise Server allowed users to migrate private repositories without having appropriate scopes defined on their Personal Access Token, enabling unauthorized repository access.

MitigationUpgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17 or later. Review existing PAT configurations to ensure proper scope limitations are enforced.

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.0, < 3.9.17>= 3.10.0, < 3.10.14>= 3.11.0, < 3.11.12>= 3.12.0, < 3.12.6= 3.13.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify GitHub Enterprise Server version
    Access the GitHub Enterprise Server management console or run 'ghe-version' command from the administrative SSH shell
    Affected if The installed version is 3.9.0 through 3.9.16, 3.10.0 through 3.10.13, 3.11.0 through 3.11.11, 3.12.0 through 3.12.5, or exactly 3.13.0
  2. Review audit logs for repository migration events
    Navigate to the Site Admin dashboard, go to Management Console > Audit Log, and search for migration-related events such as 'repo_migration.start', 'repo_migration.complete', or 'migrate' action types
    Affected if Migration events exist where the Personal Access Token used lacked the 'repo' scope but still successfully migrated a private repository
  3. Examine Personal Access Token configurations
    In the Site Admin dashboard, review user PAT configurations under 'Developer settings' > 'Personal access tokens', or query the database for PATs with scopes that do not include 'repo' but were used for migration
    Affected if PATs exist with limited scopes (lacking 'repo') that were used for repository migration operations
  4. Check for unauthorized private repository access
    Review audit logs for repository access events from migration operations, cross-referencing source and destination repositories to identify private repositories accessed without proper authorization
    Affected if Private repositories were accessed or migrated by users who did not have explicit read access to those repositories

You are affected if your GitHub Enterprise Server version falls within the listed ranges AND repository migrations were performed using Personal Access Tokens with insufficient scopes.

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.17 / 3.10.14 / 3.11.12 or later
Fixed in 3.9.173.10.143.11.12
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, or 3.9.17 or later. Review existing PAT configurations to ensure proper scope limitations are enforced.

Recommended fix High confidence

Upgrade to version 3.9.17, 3.10.14, 3.11.12, or 3.12.6 (whichever corresponds to your current release branch, or the latest available version which includes the fix)

  1. 1. Identify the currently installed GitHub Enterprise Server version by checking the management console or running: ghe-version
  2. 2. Determine which release branch you are on (3.9.x, 3.10.x, 3.11.x, or 3.12.x)
  3. 3. For version 3.9.x: upgrade to version 3.9.17
  4. 4. For version 3.10.x: upgrade to version 3.10.14
  5. 5. For version 3.11.x: upgrade to version 3.11.12
  6. 6. For version 3.12.x: upgrade to version 3.12.6
  7. 7. Review the upgrade prerequisites and backup requirements in the GitHub Enterprise Server upgrade documentation before proceeding
  8. 8. Perform the upgrade following the standard GitHub Enterprise Server upgrade procedure for your deployment type
Caveat Standard GitHub Enterprise Server upgrade considerations apply - review release notes for any migration steps or breaking changes between versions

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