LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23738: Incomplete cache verification issue in GitHub Enterprise Server leading to exposure of private repo files

An 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.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-23738 could let an authenticated GitHub Enterprise Server user expose private repository files through a public repository if an administrator visits a crafted URL. The issue is confidentiality-focused, not described as allowing code execution or data modification.

Executive priority

Treat as a priority upgrade for GHES environments containing sensitive private repositories. The issue is not described as remotely exploitable by anonymous attackers, but the potential data exposure justifies timely remediation.

Technical view

The CVE describes an improper cache key issue in GitHub Enterprise Server. Exploitation requires an authenticated user on the instance, ability to create a public repository, and administrator interaction. Fixed releases are 3.2.20, 3.3.15, 3.4.10, 3.5.7, and 3.6.3.

Likely exposure

Exposure is limited to organizations running affected GitHub Enterprise Server 3.2 through 3.6 branches before the listed fixed releases. GitHub.com and other products are not identified in the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Practical exploitation has meaningful prerequisites: local account access, public repository creation rights, and a site administrator visiting a crafted URL.

Researcher notes

The provided sources identify the vulnerability class, prerequisites, impact, affected branches, and fixed versions. They do not provide safe detection indicators, proof-of-concept details, or evidence of exploitation in the wild.

Mitigation direction

  • Inventory all GHES appliances and record exact version and branch.
  • Upgrade affected branches to 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3, or later supported releases.
  • Restrict public repository creation to trusted users until upgraded.
  • Review GitHub release notes and current vendor guidance for branch-specific upgrade instructions.

Validation and detection

  • Confirm whether GitHub Enterprise Server is deployed in the environment.
  • Compare each appliance version against the fixed release for its branch.
  • Review administrative policy for who can create public repositories.
  • Check audit logs for unusual public repository activity and administrator URL interactions where available.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-23738 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.7Medium
CVSS 3.1 vector shape for CVE-2022-23738Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitHubGitHub Enterprise Server3.2, 3.3, 3.4, 3.5, 3.6Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.