Enterprise ServerApplication · GitHub
CVE-2023-23760
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 remote code execution when building a GitHub Pages site. 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 versions 3.8 and was fixed in versions 3.7.7, 3.6.10, 3.5.14, and 3.4.17. 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 · moderate confidenceA path traversal vulnerability in GitHub Enterprise Server's GitHub Pages site building functionality allowed authenticated users with Pages creation permissions to escape intended directory boundaries and execute arbitrary code on the underlying server. The vulnerability stems from insufficient validation of file paths during the Pages build process.
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.4.17>= 3.5.0, < 3.5.14>= 3.6.0, < 3.6.10>= 3.7.0, < 3.7.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionAccess the Management Console (usually at https://hostname:8443/manage) and navigate to the Dashboard or Site Admin area to view the current version, or run `ghe-version` from the command line if you have SSH access to the instanceAffected if The installed version falls within any of these ranges: < 3.4.17, >= 3.5.0 and < 3.5.14, >= 3.6.0 and < 3.6.10, or >= 3.7.0 and < 3.7.7
-
Confirm GitHub Pages feature is enabledIn the Management Console, go to the Pages settings section (under Settings or Site Admin) and verify whether GitHub Pages site building is currently enabled for the instanceAffected if GitHub Pages is enabled and the version is vulnerable as checked in step 1
-
Review Pages creation permissionsIn the Site Admin panel, check the organization and user settings to see which users or teams have the ability to create GitHub Pages sites. Also review any site-wide policies controlling Pages creationAffected if Any user or team beyond strict administrators has Pages creation permissions, and the instance version is vulnerable and Pages is enabled
You are affected if your GitHub Enterprise Server version is one of the vulnerable releases listed AND GitHub Pages is enabled with any non-admin users having Pages 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.4.173.5.143.6.10
Upgrade GitHub Enterprise Server to version 3.7.7, 3.6.10, 3.5.14, 3.4.17, or later. Until patching is feasible, audit and restrict GitHub Pages site creation permissions to minimize attack surface.
3.4.17, 3.5.14, 3.6.10, or 3.7.7 (or latest 3.x release)
- Review the GitHub Enterprise Server upgrade prerequisites and backup documentation
- Ensure you have a complete backup of your GitHub Enterprise Server instance
- Schedule a maintenance window as upgrades require downtime
- Download the appropriate upgrade package for your current version
- For systems on 3.4.x: upgrade to version 3.4.17 or later
- For systems on 3.5.x: upgrade to version 3.5.14 or later
- For systems on 3.6.x: upgrade to version 3.6.10 or later
- For systems on 3.7.x: upgrade to version 3.7.7 or later
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 / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23760 — 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-2023-23760 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