dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-3646

HIGH · 7.2 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 3.9.13 / 3.10.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 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 instance when configuring the chat integration. 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 confidence

Command injection vulnerability in GitHub Enterprise Server's Management Console chat integration allows attackers with editor role to execute arbitrary commands and gain admin SSH access. The flaw exists in how the chat integration feature processes input, permitting shell command injection through configuration parameters.

MitigationUpgrade GitHub Enterprise Server to version 3.12.2, 3.11.8, 3.10.10, or 3.9.13 or later. Until patched, restrict Management Console access to only trusted administrators and monitor for unauthorized SSH access.

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.9.13>= 3.10.0, < 3.10.10>= 3.11.0, < 3.11.8>= 3.12.0, < 3.12.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your GitHub Enterprise Server version
    Access the Management Console or check your system documentation for the installed GHES version. Typically found in the admin settings or by running 'ghe-version' via SSH if you have admin access.
    Affected if The installed version falls within < 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.
  2. Verify the Management Console is accessible
    Confirm you can reach the Management Console login page at your-instance-hostname:8443/managementconsole or through the regular admin portal.
    Affected if The Management Console is exposed and accessible to users with editor roles.
  3. Determine if the chat integration feature is enabled
    Navigate to the Management Console settings and look for chat integration or similar messaging/collaboration configuration options. Check if any chat integration module is configured.
    Affected if The chat integration feature is enabled and configured in the Management Console.
  4. Review users with editor role permissions
    Check the Management Console user management section or the site admin dashboard for accounts granted the editor role.
    Affected if There are users assigned the editor role who have access to the chat integration configuration.
  5. Inspect chat integration configuration parameters
    In the Management Console under chat integration settings, examine any fields that accept configuration input such as webhooks, bot names, or service URLs.
    Affected if Chat integration configuration accepts user-supplied input that could be interpreted as shell commands.

You are affected if your GitHub Enterprise Server version is within the vulnerable ranges AND the Management Console chat integration feature is enabled with access granted to editor role 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.9.13 / 3.10.10 / 3.11.8 or later
Fixed in 3.9.133.10.103.11.8
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.12.2, 3.11.8, 3.10.10, or 3.9.13 or later. Until patched, restrict Management Console access to only trusted administrators and monitor for unauthorized SSH access.

Recommended fix High confidence

Upgrade to 3.12.2 (or 3.11.8/3.10.10/3.9.13 depending on your supported branch)

  1. 1. Back up your GitHub Enterprise Server instance data before proceeding with the upgrade.
  2. 2. Review the GitHub Enterprise Server upgrade prerequisites and ensure your current licensing allows for the upgrade.
  3. 3. Download the appropriate fixed version for your current branch: 3.9.13, 3.10.10, 3.11.8, or 3.12.2.
  4. 4. Follow the standard GitHub Enterprise Server upgrade procedure documented in the GitHub Enterprise Server administration documentation.
  5. 5. After upgrade, verify the Management Console is accessible and the chat integration settings can be configured without errors.
  6. 6. Confirm the instance is functioning normally and review audit logs for any suspicious activity during the vulnerable period.
Caveat Point releases typically have minimal breaking changes; review release notes for your target version for any behavior changes

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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