cve.bz

CVE-2023-6802 github enterprise server

6.5 mediumEPSS 0.7%Fix available

Medium (6.5) in github enterprise server. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
An insertion of sensitive information into the log file in the audit log in GitHub Enterprise Server was identified that could allow an attacker to gain access to the management console. To exploit this, an attacker would need access to the log files for the GitHub Enterprise Server appliance, a backup archive created with GitHub Enterprise Server Backup Utilities, or a service which received streamed logs. This vulnerability affected all versions of GitHub Enterprise Server since 3.8 and was fixed in version 3.8.12, 3.9.7, 3.10.4, and 3.11.1.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-02-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.8.12
  • GitHub Enterprise Server: fixed in 3.9.7
  • GitHub Enterprise Server: fixed in 3.10.4
  • GitHub Enterprise Server: fixed in 3.11.1

Ask an AI about this CVE

Show the promptExplain CVE-2023-6802 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-6802?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-6802?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-6802 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.8.0 through 3.8.11
GitHub Enterprise Serverfrom 3.9.0 through 3.9.6
GitHub Enterprise Serverfrom 3.10.0 through 3.10.3
GitHub Enterprise Serverfrom 3.11 through 3.11.0

Fixed in

ProductFixed in
GitHub Enterprise Server3.8.12
GitHub Enterprise Server3.9.7
GitHub Enterprise Server3.10.4
GitHub Enterprise Server3.11.1

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON