dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-8770

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to 3.10.17 / 3.11.15 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Cross-Site Scripting (XSS) vulnerability was identified in the repository transfer feature of GitHub Enterprise Server, which allows attackers to steal sensitive user information via social engineering. This vulnerability affected all versions of GitHub Enterprise Server and was fixed in version 3.10.17, 3.11.15, 3.12.9, 3.13.4, and 3.14.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 stored Cross-Site Scripting (XSS) vulnerability exists in the repository transfer feature of GitHub Enterprise Server, allowing attackers to inject malicious scripts that execute in the context of other users' sessions when they interact with the affected feature, enabling theft of sensitive user information through social engineering.

MitigationUpgrade GitHub Enterprise Server to version 3.10.17, 3.11.15, 3.12.9, 3.13.4, or 3.14.1 or later to remediate this vulnerability.

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.10.0, < 3.10.17>= 3.11.0, < 3.11.15>= 3.12.0, < 3.12.9>= 3.13.0, < 3.13.4= 3.14.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed GitHub Enterprise Server version
    Log into the GitHub Enterprise Server admin console and navigate to the Site Admin dashboard, or run 'ghe-version' from the management shell to retrieve the exact version number
    Affected if Version is 3.10.0 through 3.10.16, 3.11.0 through 3.11.14, 3.12.0 through 3.12.8, 3.13.0 through 3.13.3, or exactly 3.14.0
  2. Confirm repository transfer feature is accessible
    Navigate to any repository settings as an authenticated user and check if the 'Transfer' option appears under the repository General settings
    Affected if The repository transfer feature is available and users can access it
  3. Verify admin has not restricted transfer capabilities
    As a site admin, go to the Admin Center > Repository > Repository transfers settings to see if transfer functionality is enabled organization-wide
    Affected if Repository transfers are not explicitly disabled at the site level

You are affected if your GitHub Enterprise Server version falls within the vulnerable ranges AND the repository transfer feature is accessible to users.

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.10.17 / 3.11.15 / 3.12.9 or later
Fixed in 3.10.173.11.153.12.9
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.10.17, 3.11.15, 3.12.9, 3.13.4, or 3.14.1 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to 3.10.17, 3.11.15, 3.12.9, 3.13.4, or 3.14.1+ (choose the appropriate version for your release line)

  1. 1. Identify the current GitHub Enterprise Server version by checking the administrative UI or running: ghe-version
  2. 2. Based on the current version, determine the appropriate target upgrade path:
  3. - If running 3.10.x (where x is 0-16): upgrade to 3.10.17
  4. - If running 3.11.x (where x is 0-14): upgrade to 3.11.15
  5. - If running 3.12.x (where x is 0-8): upgrade to 3.12.9
  6. - If running 3.13.x (where x is 0-3): upgrade to 3.13.4
  7. - If running 3.14.0: upgrade to 3.14.1 or later
  8. 3. Review the GitHub Enterprise Server upgrade prerequisites and backup requirements
Caveat Review GitHub Enterprise Server release notes for your target version for any breaking changes or required migration steps

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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