Enterprise ServerApplication · GitHub
CVE-2024-5815
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 Cross-Site Request Forgery vulnerability in GitHub Enterprise Server allowed write operations on a victim-owned repository by exploiting incorrect request types. A mitigating factor is that the attacker would have to be a trusted GitHub Enterprise Server user, and the victim would have to visit a tag in the attacker's fork of their own repository. vulnerability affected all versions of GitHub Enterprise Server prior 3.14 and was fixed in version 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in GitHub Enterprise Server allowed authenticated attackers to perform unauthorized write operations on victim-owned repositories by exploiting incorrect HTTP request type handling. The attack required the victim to visit a tag in the attacker's fork of their own repository.
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.0, < 3.9.17>= 3.10.0, < 3.10.14>= 3.11.0, < 3.11.12>= 3.12.0, < 3.12.6= 3.13.0CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionAccess the GitHub Enterprise Server management console or run the command `ghe-version` via SSH to the GHES instanceAffected if The version returned is within any of these ranges: 3.9.0 to 3.9.16, 3.10.0 to 3.10.13, 3.11.0 to 3.11.11, 3.12.0 to 3.12.5, or exactly 3.13.0
-
Verify user authentication settingsReview the authentication configuration in the GitHub Enterprise Server management console under 'Authentication' settingsAffected if User authentication is enabled and users can create or manage forks of their own repositories
-
Check for fork creation permissionsNavigate to site admin settings, review 'Repository management' policies to see if users are allowed to create forksAffected if Fork creation is enabled for users, particularly forks of their own repositories
-
Assess fork and tag exposureAudit repository forks and tags in the environment using administrative APIs or by reviewing high-traffic repositories for suspicious fork-tag combinationsAffected if Users have created forks of their own repositories and those forks contain tags that other users could be tricked into visiting
The environment is affected if the installed GitHub Enterprise Server version falls within the vulnerable ranges listed and fork creation with tags is enabled, allowing an attacker to exploit the CSRF vulnerability by tricking a victim into visiting a tag in the attacker's fork.
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.173.10.143.11.12
Upgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, 3.9.17, or later to address the CSRF vulnerability.
Upgrade to version 3.9.17, 3.10.14, 3.11.12, 3.12.6, or 3.13.1 or later (preferably the latest 3.13.x release)
- 1. Identify your current GitHub Enterprise Server version in the Admin Center (go to Site admin > Configuration > About)
- 2. Determine the appropriate upgrade path based on your current version (see affected versions list)
- 3. Review GitHub Enterprise Server upgrade prerequisites and backup your instance
- 4. Download the target fixed version (3.9.17, 3.10.14, 3.11.12, 3.12.6, or 3.13.1 or later)
- 5. Schedule a maintenance window and put your instance in maintenance mode
- 6. Follow the official GitHub Enterprise Server upgrade procedure for your infrastructure
- 7. After upgrade completes, verify the version in the Admin Center and disable maintenance mode
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-5815 — 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-5815 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