Enterprise ServerApplication · GitHub
CVE-2024-3684
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 an editor role in the Management Console to gain admin access to the appliance when configuring the Artifacts & Logs and Migrations Storage. Exploitation of this vulnerability required access to the GitHub Enterprise Server instance and access to the Management Console with the editor role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.12.2, 3.11.8, 3.10.10, and 3.9.13. 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's Management Console allows users with editor role to inject malicious requests when configuring Artifacts & Logs and Migrations Storage settings, enabling privilege escalation to admin access on the appliance.
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.13>= 3.10.0, < 3.10.10>= 3.11.0, < 3.11.8>= 3.12.0, < 3.12.2CVSS 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.
-
Identify GitHub Enterprise Server versionAccess the Management Console or use the administrative API to retrieve the current GitHub Enterprise Server version number. This is typically visible on the Management Console dashboard or can be obtained via administrative commands.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.2
-
Verify Management Console accessReview the Management Console access controls and authentication settings to determine who can reach the console interface.Affected if Users other than intended administrators can access the Management Console
-
Enumerate editor role usersReview user accounts and their assigned roles within the GitHub Enterprise Server administration interface. Look for users granted the editor role.Affected if There are users assigned the editor role who have access to Management Console settings
-
Inspect Artifacts & Logs storage configurationNavigate to the Management Console settings and examine the current configuration for Artifacts & Logs storage. Look for any unexpected or suspicious URLs configured in this section.Affected if The Artifacts & Logs storage setting is configured with a URL pointing to internal infrastructure or an unexpected external location
-
Inspect Migrations Storage configurationNavigate to the Management Console settings and examine the current configuration for Migrations Storage. Look for any unexpected or suspicious URLs configured in this section.Affected if The Migrations Storage setting is configured with a URL pointing to internal infrastructure or an unexpected external location
A user is affected if their GitHub Enterprise Server version is within the affected ranges AND the Management Console is accessible to editor role users who can configure the Artifacts & Logs or Migrations Storage settings.
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.133.10.103.11.8
Upgrade GitHub Enterprise Server to version 3.12.2, 3.11.8, 3.10.10, or 3.9.13 or later. Additionally, restrict Management Console access to only necessary personnel and monitor for suspicious configuration changes.
Upgrade to 3.12.2 (or the latest fixed version in your current release line: 3.9.13, 3.10.10, or 3.11.8)
- 1. Backup your GitHub Enterprise Server instance before starting the upgrade process.
- 2. Identify your current GitHub Enterprise Server version from the Administrative Center (Settings > About).
- 3. Plan the upgrade path based on your current version: if on 3.9.x line, upgrade to 3.9.13; if on 3.10.x line, upgrade to 3.10.10; if on 3.11.x line, upgrade to 3.11.8; if on 3.12.x line, upgrade to 3.12.2.
- 4. Download the appropriate upgrade package from GitHub's download portal (https://enterprise.github.com/releases).
- 5. Follow GitHub's standard upgrade procedure: run the upgrade script or use the management console web interface to apply the update.
- 6. After upgrade completes, verify the Management Console is accessible and the version reflects the patched release.
- 7. Review Management Console settings for Artifacts & Logs and Migrations Storage configurations to confirm they were not tampered with during any potential prior exploitation.
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
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 locallyCheck whether your project pulls in CVE-2024-3684 — 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-3684 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