Enterprise ServerApplication · GitHub
CVE-2024-5746
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 · uneditedA Server-Side Request Forgery vulnerability was identified in GitHub Enterprise Server that allowed an attacker with the Site Administrator role to gain arbitrary code execution capability on the GitHub Enterprise Server instance. Exploitation required authenticated access to GitHub Enterprise Server as a user with the Site Administrator role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.13 and was fixed in versions 3.12.5, 3.11.11, 3.10.13, and 3.9.16. 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 confidenceA Server-Side Request Forgery (SSRF) vulnerability in GitHub Enterprise Server allowed authenticated Site Administrators to trigger arbitrary server-side requests that led to remote code execution. The attacker exploited the SSRF to gain full code execution capability on the instance.
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
< 3.9.16>= 3.10.0, < 3.10.13>= 3.11.0, < 3.11.11>= 3.12.0, < 3.12.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check GitHub Enterprise Server versionNavigate to the Management Console (usually at /setup) and view the footer, or access the Site Admin dashboard and check the 'About' page. Alternatively, run 'ghe-version' from the administrative SSH console if available.Affected if The installed version falls into any of these ranges: < 3.9.16, >= 3.10.0 and < 3.10.13, >= 3.11.0 and < 3.11.11, or >= 3.12.0 and < 3.12.5.
-
Identify Site Administrator accountsIn the Site Admin dashboard, go to the 'Users' or 'Site Admin' settings and list all accounts with Site Administrator privileges. Review the list for any unexpected or unauthorized administrators.Affected if There exist Site Administrator accounts beyond those intentionally created by your organization, indicating potential compromise.
-
Verify multi-factor authentication on admin accountsIn the Site Admin dashboard, review each Site Administrator account's security settings to confirm whether multi-factor authentication (MFA) is enabled.Affected if Any Site Administrator account lacks multi-factor authentication enabled, making credential theft more viable for exploitation.
-
Review audit logs for suspicious admin activityIn the Site Admin dashboard, access the 'Audit Log' and filter for actions performed by Site Administrators, particularly looking for unexpected API calls, webhook creation, or network requests.Affected if Audit logs show anomalous network requests or API calls from admin sessions that were not initiated by legitimate administrators.
You are affected if your GitHub Enterprise Server version is below 3.9.16, between 3.10.0-3.10.12, between 3.11.0-3.11.10, or between 3.12.0-3.12.4 AND an attacker with Site Administrator credentials could exploit the SSRF to achieve remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.9.163.10.133.11.11
Upgrade GitHub Enterprise Server to version 3.12.5, 3.11.11, 3.10.13, or 3.9.16 (or later) to remediate this vulnerability. Since the attack requires Site Administrator credentials, ensure such accounts use strong, unique passwords and enable multi-factor authentication.
3.12.5 (or the latest fixed version in your current release line: 3.9.16, 3.10.13, or 3.11.11)
- 1. Back up your GitHub Enterprise Server instance data before proceeding with any upgrade.
- 2. Identify your current GitHub Enterprise Server version by navigating to the Management Console or running the administrative API.
- 3. Determine which upgrade path applies to your current version: if you're on 3.9.x, upgrade to 3.9.16; if on 3.10.x, upgrade to 3.10.13; if on 3.11.x, upgrade to 3.11.11; if on 3.12.x, upgrade to 3.12.5.
- 4. Download the appropriate upgrade package from the GitHub Enterprise Server releases page.
- 5. Follow GitHub's standard upgrade procedure: put the instance in maintenance mode, run the upgrade package, verify the upgrade completed successfully, and then disable maintenance mode.
- 6. After upgrade, verify the instance is running the patched version and confirm all services are operational.
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
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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