dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-1084

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 3.8.15 / 3.9.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site Scripting in the tag name pattern field in the tag protections UI in GitHub Enterprise Server allows a malicious website that requires user interaction and social engineering to make changes to a user account via CSP bypass with created CSRF tokens. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12  and was fixed in all versions of 3.11.5, 3.10.7, 3.9.10, and 3.8.15. 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 is a stored Cross-site Scripting (XSS) vulnerability in the tag name pattern field within GitHub Enterprise Server's tag protections UI. The attack requires user interaction and social engineering, combined with Content Security Policy (CSP) bypass and crafted CSRF tokens to make unauthorized changes to a user account.

MitigationUpgrade GitHub Enterprise Server to version 3.11.5, 3.10.7, 3.9.10, 3.8.15 or later to remediate this 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.15>= 3.9.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 management console or run 'ghe-version' command via SSH to the instance. Check the Admin Center under 'About' section for the exact version number.
    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, or >= 3.11.0 and < 3.11.5
  2. Verify tag protections are accessible
    Navigate to a repository's Settings > Tags > Tag protection rules, or check if the account has permissions to manage tag protection patterns.
    Affected if Tag protection rule management is available and the user has privileges to create or edit tag name patterns
  3. Identify the affected component
    Locate the 'tag name pattern' input field within the tag protection rules UI for any repository or organization.
    Affected if The tag name pattern field exists and accepts user input for creating protection rules

You are affected if your GitHub Enterprise Server version is below 3.8.15, between 3.9.0-3.9.9, between 3.10.0-3.10.6, or between 3.11.0-3.11.4, and you have users with access to tag protection rule management.

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.15 / 3.9.10 / 3.10.7 or later
Fixed in 3.8.153.9.103.10.7
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.11.5, 3.10.7, 3.9.10, 3.8.15 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to version 3.8.15, 3.9.10, 3.10.7, or 3.11.5 depending on your current version branch

  1. 1. Identify the current GitHub Enterprise Server version by navigating to the admin console or running: ghe-version
  2. 2. Determine the appropriate target version based on current version: if < 3.8.15 upgrade to 3.8.15; if >= 3.9.0 and < 3.9.10 upgrade to 3.9.10; if >= 3.10.0 and < 3.10.7 upgrade to 3.10.7; if >= 3.11.0 and < 3.11.5 upgrade to 3.11.5
  3. 3. Review the GitHub Enterprise Server release notes for the target version to check for any breaking changes or required migration steps
  4. 4. Take a backup of the GitHub Enterprise Server instance following standard backup procedures
  5. 5. Upgrade to the target version using the standard GitHub Enterprise Server upgrade process (e.g., using the upgrade package or admin console)
  6. 6. After upgrade, verify the version has been updated successfully and the tag protections UI is functioning correctly
Caveat Review release notes for version-specific breaking changes; major version upgrades may include feature changes or require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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