Enterprise ServerApplication · GitHub
CVE-2024-1369
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 command injection vulnerability was identified in GitHub Enterprise Server that allowed an attacker with an editor role in the Management Console to gain admin SSH access to the appliance when setting the username and password for collectd configurations. 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.11.5, 3.10.7, 3.9.10, and 3.8.15. This vulnerability was reported via the GitHub Bug Bounty program https://bounty.github.com .
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 command injection vulnerability in GitHub Enterprise Server's Management Console allows attackers with editor role to execute arbitrary commands via username and password fields for collectd configurations, enabling admin SSH access to 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.8.15>= 3.9.0, < 3.9.10>= 3.10.0, < 3.10.7>= 3.11.0, < 3.11.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 installationCheck if GitHub Enterprise Server is running in your environment. This may be visible in your infrastructure inventory, running services, or by accessing the web interface and checking the footer for version information.Affected if GitHub Enterprise Server is not installed, the system is not affected by this CVE.
-
Determine installed versionAccess the Management Console (typically at /setup) or check the administrative interface for the exact version number. Compare against the affected ranges: < 3.8.15, 3.9.0-3.9.9, 3.10.0-3.10.6, or 3.11.0-3.11.4.Affected if The installed version falls within any of these ranges: < 3.8.15, >= 3.9.0 and < 3.9.10, >= 3.10.0 and < 3.10.7, >= 3.11.0 and < 3.11.5.
-
Verify Management Console access controlsReview user accounts and their roles in the Management Console. Check which users have the editor role assigned, as this role is required to exploit the vulnerability.Affected if Any user account has editor role access to the Management Console and the version is affected.
-
Inspect collectd configuration settingsIn the Management Console, navigate to the collectd configuration section (typically under Monitoring or Diagnostics settings). Examine whether username and password fields are present and configurable for collectd.Affected if Collectd configuration with editable username and password fields is accessible to an editor role account on an affected version.
You are affected if you run a GitHub Enterprise Server version within the affected ranges AND have any user with editor role able to access the Management Console collectd configuration 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.8.153.9.103.10.7
Upgrade GitHub Enterprise Server to version 3.11.5, 3.10.7, 3.9.10, or 3.8.15 or later. Until patched, strictly limit Management Console access to trusted administrators only and audit existing editor accounts.
3.11.5 (or newer if available - fixed in 3.8.15, 3.9.10, 3.10.7, and 3.11.5)
- Back up your GitHub Enterprise Server instance data and configuration before proceeding with any upgrade
- Schedule a maintenance window as upgrades require downtime
- Download the appropriate upgrade package for your target version (3.8.15, 3.9.10, 3.10.7, or 3.11.5) from the GitHub Enterprise downloads portal
- Access the Management Console at /setup by logging in as an admin
- Navigate to the settings or upgrade section and upload the upgrade package
- Follow the on-screen prompts to complete the installation
- After upgrade completes, verify the instance is operational and test that the Management Console is accessible
- Review user roles in the Management Console to ensure only trusted personnel have editor access
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1369 — 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-1369 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