Enterprise ServerApplication · GitHub
CVE-2024-1082
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 path traversal vulnerability was identified in GitHub Enterprise Server that allowed an attacker to gain unauthorized read permission to files by deploying arbitrary symbolic links to a GitHub Pages site with a specially crafted artifact tarball. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.8.15, 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 confidenceA path traversal vulnerability in GitHub Enterprise Server allowed authenticated users with GitHub Pages site creation permissions to deploy arbitrary symbolic links via specially crafted artifact tarballs, enabling unauthorized read access to files outside the intended Pages directory.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Determine your GitHub Enterprise Server versionAccess the GitHub Enterprise Server administration console or run 'ghe-version' via SSH to the appliance. The version is also visible on the site administration dashboard under the help menu.Affected if The installed version falls into 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 if GitHub Pages is enabledNavigate to the site administration settings. GitHub Pages must be enabled for this vulnerability to be exploitable. Check Site Admin > Settings > Pages, or query via the management console.Affected if GitHub Pages is enabled on the instance and the version is in the affected ranges listed above
-
Identify users with Pages site creation permissionsReview organization and site admin permissions. Users with the ability to create or modify GitHub Pages sites include organization owners, repository admins with Pages enabled, and any custom roles granting Pages creation. Check the organizations and repositories where Pages is active.Affected if Any user with Pages creation permissions is untrusted or has external collaborator status, and the GitHub Enterprise Server version is in the affected ranges
-
Audit Pages repositories for unexpected symbolic linksExamine recently created or modified GitHub Pages repositories. Look for symbolic links that point outside the repository or Pages publish directory. Use 'ls -la' in the Pages git repository or check the Pages publish branch for symlinks targeting parent directories (e.g., ../../../etc/passwd).Affected if Symmetric links exist in Pages repositories that point to paths outside the intended Pages directory, indicating potential exploitation
Your environment is affected if GitHub Pages is enabled, your installed GitHub Enterprise Server version is less than 3.8.15, or falls within 3.9.0-3.9.9, 3.10.0-3.10.6, or 3.11.0-3.11.4, and untrusted users have Pages site creation permissions.
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.12 or later, or to one of the patched versions (3.8.15, 3.9.10, 3.10.7, 3.11.5). Ensure only trusted users have GitHub Pages site creation permissions until the patch is applied.
Upgrade to version 3.8.15 (if on 3.7.x), 3.9.10 (if on 3.9.x), 3.10.7 (if on 3.10.x), 3.11.5 (if on 3.11.x), or preferably 3.12.x (latest stable)
- Identify current GitHub Enterprise Server version by navigating to the admin console or running 'ghe-version' command
- Determine the appropriate upgrade path based on current version (see upgrade_path for target versions)
- Schedule a maintenance window and create a backup of the GitHub Enterprise Server instance
- For versions < 3.8.15: Upgrade to 3.8.15 or higher (3.12.x recommended)
- For versions >= 3.9.0 and < 3.9.10: Upgrade to 3.9.10 or higher (3.12.x recommended)
- For versions >= 3.10.0 and < 3.10.7: Upgrade to 3.10.7 or higher (3.12.x recommended)
- For versions >= 3.11.0 and < 3.11.5: Upgrade to 3.11.5 or higher (3.12.x recommended)
- Follow GitHub Enterprise Server upgrade documentation for your infrastructure (VMware, AWS, Azure, etc.)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1082 — 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-1082 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