dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1482

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 3.9.10 / 3.10.7 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 incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an attacker to create new branches in public repositories and run arbitrary GitHub Actions workflows with permissions from the GITHUB_TOKEN. To exploit this vulnerability, an attacker would need access to the Enterprise Server. This vulnerability affected all versions of GitHub Enterprise Server after 3.8 and prior to 3.12, and was fixed in versions 3.9.10, 3.10.7, 3.11.5. 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

An incorrect authorization vulnerability in GitHub Enterprise Server allowed authenticated users with access to the Enterprise to create branches in public repositories and execute arbitrary GitHub Actions workflows using GITHUB_TOKEN permissions. This authorization bypass allowed attackers to circumvent intended access controls on public repository operations.

MitigationUpgrade GitHub Enterprise Server to versions 3.9.10, 3.10.7, 3.11.5, or later to remediate the vulnerability.

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.0, < 3.9.10>= 3.10.0, < 3.10.7>= 3.11.0, < 3.11.5

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Identify GitHub Enterprise Server version
    Access the GitHub Enterprise Server Admin Center (https://[hostname]/setup/settings) or run 'ghe-version' in the management shell to retrieve the installed version number
    Affected if The installed version is >= 3.8.0 and < 3.9.10, OR >= 3.10.0 and < 3.10.7, OR >= 3.11.0 and < 3.11.5
  2. Confirm presence of public repositories
    Use the GitHub Enterprise admin API endpoint '/orgs/{org}/repos' or navigate to the organization settings to list repositories and identify any with 'public' visibility
    Affected if There exists at least one public repository within any organization in the Enterprise
  3. Verify authenticated user branch creation capability in public repos
    Using a test user account with basic Enterprise membership but without repository admin privileges, attempt to create a new branch in a public repository via the web UI, API (POST /repos/{owner}/{repo}/git/refs), or git push
    Affected if The user can successfully create a branch in a public repository they do not own or have admin rights to
  4. Verify GitHub Actions workflow execution on branch creation
    Configure a workflow in a public repository that triggers on 'create' events and uses GITHUB_TOKEN, then have an authenticated Enterprise member create a branch and confirm the workflow executes with token permissions
    Affected if Workflows can be triggered and execute with GITHUB_TOKEN permissions when branches are created by users without explicit repository write access

The environment is affected if running a vulnerable GitHub Enterprise Server version AND there are public repositories where authenticated Enterprise users can create branches, enabling unauthorized workflow execution.

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.10 / 3.10.7 / 3.11.5 or later
Fixed in 3.9.103.10.73.11.5
Interim mitigation

Upgrade GitHub Enterprise Server to versions 3.9.10, 3.10.7, 3.11.5, or later to remediate the vulnerability.

Recommended fix High confidence

3.9.10 (for 3.8.x/3.9.x branches), 3.10.7 (for 3.10.x branch), or 3.11.5 (for 3.11.x branch)

  1. 1. Identify the currently installed GitHub Enterprise Server version by navigating to the administrative UI or running: ghe-version
  2. 2. Determine which version branch you are currently on (3.8.x, 3.9.x, 3.10.x, or 3.11.x)
  3. 3. For version 3.8.x: Upgrade directly to 3.9.10 or later (recommended: 3.9.10)
  4. 4. For version 3.9.x (prior to 3.9.10): Upgrade to 3.9.10 or later (recommended: 3.9.10)
  5. 5. For version 3.10.x (prior to 3.10.7): Upgrade to 3.10.7 or later (recommended: 3.10.7)
  6. 6. For version 3.11.x (prior to 3.11.5): Upgrade to 3.11.5 or later (recommended: 3.11.5)
  7. 7. Follow the standard GitHub Enterprise Server upgrade procedure using GitHub's official upgrade documentation
  8. 8. After upgrade, verify the version with: ghe-version
Caveat Standard GitHub Enterprise Server upgrade considerations apply: review release notes for breaking changes, ensure backup of data, plan maintenance window as upgrades may require downtime

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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