dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1908

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 3.8.16 / 3.9.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An Improper Privilege Management vulnerability was identified in GitHub Enterprise Server that allowed an attacker to use the Enterprise Actions GitHub Connect download token to fetch private repository data. An attacker would require an account on the server instance with non-default settings for GitHub Connect. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.8.16, 3.9.11, 3.10.8, and 3.11.6. 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

This improper privilege management vulnerability in GitHub Enterprise Server allowed the Enterprise Actions GitHub Connect download token to be used beyond its intended scope, enabling an authenticated attacker with non-default GitHub Connect settings to fetch private repository data that should have been restricted.

MitigationUpgrade to GitHub Enterprise Server version 3.8.16, 3.9.11, 3.10.8, 3.11.6, or 3.12 or later. Additionally, audit GitHub Connect configuration settings and review access logs for any unauthorized access using the download token.

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.8.16>= 3.9.0, < 3.9.11>= 3.10.0, < 3.10.8>= 3.11.0, < 3.11.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check GitHub Enterprise Server version
    Access the GitHub Enterprise Server admin console or use the administrative shell command: ghe-version. Alternatively, check the version displayed on the sign-in page or in the Management Console under 'About GitHub Enterprise'.
    Affected if The installed version is less than 3.8.16, or between 3.9.0 and 3.9.11 inclusive, or between 3.10.0 and 3.10.8 inclusive, or between 3.11.0 and 3.11.6 inclusive.
  2. Verify if GitHub Connect is enabled
    Navigate to the GitHub Enterprise Server Management Console, then go to 'GitHub Connect' settings. Alternatively, use the administrative API endpoint /setup/api/settings to query the 'github-connect' setting.
    Affected if GitHub Connect is enabled and configured with non-default settings, particularly where 'Enable access to private repositories' or similar private repository access options are enabled.
  3. Audit GitHub Connect download token usage
    Review Enterprise audit logs for API calls using the 'download' token scope, filtering for events from the 'github_connect' category. Look for access to private repository endpoints that may indicate the token was used beyond its intended Actions workflow download scope.
    Affected if There are audit log entries showing the download token accessing private repository data outside of Actions workflow artifact retrieval.

A user is affected if their GitHub Enterprise Server version falls within the affected ranges AND GitHub Connect is enabled with non-default settings that allow broader private repository access than intended.

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.8.16 / 3.9.11 / 3.10.8 or later
Fixed in 3.8.163.9.113.10.8
Interim mitigation

Upgrade to GitHub Enterprise Server version 3.8.16, 3.9.11, 3.10.8, 3.11.6, or 3.12 or later. Additionally, audit GitHub Connect configuration settings and review access logs for any unauthorized access using the download token.

Recommended fix High confidence

3.11.6 (or nearest fixed version for your current branch: 3.8.16, 3.9.11, or 3.10.8)

  1. 1. Back up your GitHub Enterprise Server instance according to official backup procedures
  2. 2. Review the current GitHub Connect settings in your instance admin console
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Download the appropriate patched version from GitHub Enterprise downloads (3.8.16, 3.9.11, 3.10.8, or 3.11.6)
  5. 5. Follow the GitHub Enterprise Server upgrade instructions for your deployment type
  6. 6. After upgrade, verify that GitHub Connect functionality is working correctly
  7. 7. Review audit logs to confirm no unauthorized access occurred during the vulnerable period
Caveat Standard GitHub Enterprise Server upgrade considerations apply; 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
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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