dbcve.org
Enterprise ServerApplication · GitHub

CVE-2023-6746

MEDIUM · 5.7 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 3.7.19 / 3.8.12 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
An insertion of sensitive information into log file vulnerability was identified in the log files for a GitHub Enterprise Server back-end service that could permit an `adversary in the middle attack` when combined with other phishing techniques. 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.7 and was fixed in version 3.7.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1. 

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 confidence

Sensitive information is being written to log files in a GitHub Enterprise Server back-end service. An attacker with access to the log files (via the appliance, backup archives, or streamed logs) could obtain this information and combine it with MITM/phishing attacks.

MitigationUpgrade to GitHub Enterprise Server versions 3.7.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.1. Additionally, restrict access to log files and secure backup archives.

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
Affected:>= 3.7.0, < 3.7.19>= 3.8.0, < 3.8.12>= 3.9.0, < 3.9.7>= 3.10.0, < 3.10.4= 3.11.0

CVSS 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
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check GitHub Enterprise Server version via admin console
    Log into the GitHub Enterprise Server management console and navigate to the 'About' or 'Version' section to view the installed version
    Affected if Version is 3.7.0 through 3.7.18, 3.8.0 through 3.8.11, 3.9.0 through 3.9.6, 3.10.0 through 3.10.3, or exactly 3.11.0
  2. Check GitHub Enterprise Server version via command line
    Run 'ghe-version' or 'cat /etc/github/build_version' on the appliance command line
    Affected if Version matches any of the affected ranges listed above
  3. Inspect log file locations
    Examine standard GitHub Enterprise log directories such as /var/log/github/, /data/user/logs/, or logs accessible via the management console
    Affected if Log files exist on the system (the vulnerability writes sensitive data to logs in affected versions)

If the installed GitHub Enterprise Server version falls within any of the affected ranges (3.7.0-3.7.18, 3.8.0-3.8.11, 3.9.0-3.9.6, 3.10.0-3.10.3, or 3.11.0), sensitive information may be present in log files and the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.7.19 / 3.8.12 / 3.9.7 or later
Fixed in 3.7.193.8.123.9.7
Interim mitigation

Upgrade to GitHub Enterprise Server versions 3.7.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.1. Additionally, restrict access to log files and secure backup archives.

Recommended fix High confidence

Upgrade to version 3.7.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.1 (latest) based on your current major version branch

  1. 1. Back up your GitHub Enterprise Server instance and verify backup integrity before proceeding
  2. 2. Download the appropriate upgrade package for your current version from GitHub's release page or your GitHub Enterprise license portal
  3. 3. Access the GitHub Enterprise Server management console and navigate to the upgrade settings
  4. 4. Upload and apply the upgrade package (3.7.19, 3.8.12, 3.9.7, or 3.10.4 depending on your current major version, or 3.11.1 for the latest)
  5. 5. Wait for the upgrade to complete and the instance to restart
  6. 6. Verify the upgrade was successful by checking the management console status and reviewing the version number
  7. 7. Review new log files to confirm sensitive information is no longer being logged
Caveat Standard GitHub Enterprise Server upgrade precautions apply; ensure backups are verified and plan for appropriate maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6746 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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