Security readout for executives and security teams
Plain-English summary
An authenticated user with permission to create and build GitHub Pages on GitHub Enterprise Server could read files the server should protect. The main business risk is disclosure of sensitive local files. This is not described as unauthenticated remote code execution, but affected instances should be patched promptly.
Executive priority
Treat this as a timely patching item for self-hosted GitHub Enterprise Server, especially where many internal users can build Pages sites. Prioritize by sensitivity of data on the GHES appliance and breadth of Pages permissions, not by internet exposure alone.
Technical view
CVE-2023-22380 is a CWE-22 path traversal flaw in GitHub Enterprise Server’s GitHub Pages site build flow. The CVSS 3.1 score is 6.5: network-reachable, low complexity, low privileges, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact reported.
Likely exposure
Exposure is limited to GitHub Enterprise Server environments running affected versions since 3.7 where GitHub Pages site creation and builds are available to users. Internet exposure is less important than whether an attacker has a valid account with Pages build permission.
Exploitation context
The provided sources do not show active exploitation and the CVE is not marked KEV. Exploitation requires permission to create and build a GitHub Pages site on the target GitHub Enterprise Server instance. Evidence does not identify public exploit code or broader unauthenticated attack paths.
Researcher notes
The available record is concise and does not describe affected file paths, exploit primitives, or branch-specific fixes beyond the 3.7.6 release note reference. Analysis should stay focused on GHES Pages build authorization, version status, and confidentiality exposure. Do not assume integrity or availability impact from the cited CVSS vector.
Mitigation direction
- Upgrade affected GitHub Enterprise Server 3.7 deployments to version 3.7.6 or later vendor-fixed guidance.
- Check GitHub’s release notes for the correct fixed release for your supported GHES branch.
- Restrict GitHub Pages creation and build permissions until the instance is confirmed fixed.
- Review who can create and build Pages sites on the enterprise instance.
Validation and detection
- Confirm the GitHub Enterprise Server version and whether it is below the fixed 3.7.6 release.
- Verify whether GitHub Pages is enabled on the instance.
- Identify users or groups with permission to create and build GitHub Pages sites.
- After upgrade, confirm the appliance reports the intended fixed version.
- Review relevant audit logs for unusual Pages build activity where available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-22380 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.github.com/en/enterprise-server%403.7/admin/release-notes#3.7.6CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.