Enterprise ServerApplication · GitHub
CVE-2022-23738
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 · uneditedAn improper cache key vulnerability was identified in GitHub Enterprise Server that allowed an unauthorized actor to access private repository files through a public repository. To exploit this, an actor would need to already be authorized on the GitHub Enterprise Server instance, be able to create a public repository, and have a site administrator visit a specially crafted URL. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.6 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3. 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 confidenceAn improper cache key vulnerability in GitHub Enterprise Server allows an authorized user who can create a public repository to access private repository files by exploiting how the system caches content. The attack requires tricking a site administrator into visiting a specially crafted URL, leveraging the cache key flaw to bypass access controls.
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.2.0, < 3.2.20>= 3.3.0, < 3.3.15>= 3.4.0, < 3.4.10>= 3.5.0, < 3.5.7>= 3.6.0, < 3.6.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 versionRun the command to display the GitHub Enterprise Server version (typically via the management console or administrative shell). Compare the version number against the affected ranges: 3.2.0 to 3.2.19, 3.3.0 to 3.3.14, 3.4.0 to 3.4.9, 3.5.0 to 3.5.6, and 3.6.0 to 3.6.2.Affected if The installed version falls within any of these ranges.
-
Verify public repository creation policyCheck the organization or instance settings to determine whether public repository creation is permitted for authorized users.Affected if Public repository creation is enabled for users who are not site administrators.
-
Review audit and access logs for suspicious cache-related requestsSearch server logs for unusual URL patterns involving cache keys that may indicate exploitation attempts, such as requests attempting to access private repository content through crafted public repository paths.Affected if Logs contain requests with manipulated cache keys accessing private repository data from non-privileged accounts.
-
Inspect for unauthorized private repository accessExamine access logs and cache entries to identify if any private repository content was served to users without proper authorization, particularly following public repository creation.Affected if Private repository files were accessed by users lacking permission, occurring after a public repository was created by that user.
A user is affected if GitHub Enterprise Server version is within the affected ranges AND public repository creation is permitted, allowing an authorized user to potentially access private repository files through the cache key flaw.
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.2.203.3.153.4.10
Upgrade GitHub Enterprise Server to version 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3, or later to resolve the improper cache key vulnerability.
Upgrade to GitHub Enterprise Server 3.6.3 or later (or at minimum 3.5.7/3.4.10/3.3.15/3.2.20 depending on your current major version branch)
- 1. Back up your GitHub Enterprise Server instance data before proceeding with any upgrade.
- 2. Review the GitHub Enterprise Server upgrade prerequisites and ensure your system meets the requirements.
- 3. Plan for maintenance window as upgrade will require downtime.
- 4. Download the appropriate fixed version from GitHub Enterprise downloads (3.2.20, 3.3.15, 3.4.10, 3.5.7, or 3.6.3).
- 5. Follow the standard GitHub Enterprise Server upgrade procedure for your deployment type (VM or cloud).
- 6. After upgrade, verify the instance is operational and test that the vulnerability is no longer present.
- 7. Review audit logs for any suspicious activity that may indicate exploitation attempts prior to the upgrade.
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
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23738 — 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-2022-23738 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