Enterprise ServerApplication · GitHub
CVE-2021-22867
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 could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. 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.1.3 and was fixed in 3.1.3, 3.0.11, and 2.22.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 · high confidenceA path traversal vulnerability in GitHub Enterprise Server allows authenticated users with GitHub Pages permissions to read arbitrary files on the server by manipulating user-controlled configuration options used during GitHub Pages site builds.
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
< 2.22.17>= 3.0.0, < 3.0.11>= 3.1.0, < 3.1.3CVSS 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.
-
Identify GitHub Enterprise Server versionCheck the version of your GitHub Enterprise Server installation using the administrative interface or the `ghe-version` command if available in your management consoleAffected if The installed version falls within < 2.22.17, >= 3.0.0 and < 3.0.11, or >= 3.1.0 and < 3.1.3
-
Confirm GitHub Pages is enabledVerify whether the GitHub Pages feature is enabled in your GitHub Enterprise Server instance through the admin settings or management consoleAffected if GitHub Pages is enabled and the server version is vulnerable as identified above
-
Review GitHub Pages user permissionsAudit user accounts that have GitHub Pages permissions or the ability to create/modify GitHub Pages sites within your instanceAffected if There are users with GitHub Pages permissions on a vulnerable version, allowing them to potentially exploit the path traversal
-
Check for suspicious GitHub Pages configurationsReview recent GitHub Pages site builds or configuration changes for unusual file paths or attempts to access system directories outside the expected build environmentAffected if Any GitHub Pages configuration files or build logs show attempts to access arbitrary filesystem paths
Your environment is affected if you are running a vulnerable GitHub Enterprise Server version (below 2.22.17, 3.0.0-3.0.10, or 3.1.0-3.1.2) with GitHub Pages enabled and users who have GitHub Pages 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.
From vendor data2.22.173.0.113.1.3
Upgrade GitHub Enterprise Server to version 3.1.3, 3.0.11, or 2.22.17 (or later). Review GitHub Pages access controls and monitor for any unauthorized access attempts on unpatched instances.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22867 — 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-2021-22867 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