dbcve.org
Enterprise ServerApplication · GitHub

CVE-2023-46646

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Improper access control in all versions of GitHub Enterprise Server allows unauthorized users to view private repository names via the "Get a check run" API endpoint. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected GitHub Enterprise Server version 3.7.0 and above and was fixed in version 3.17.19, 3.8.12, 3.9.7 3.10.4, and 3.11.0.

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

Improper access control in GitHub Enterprise Server allows unauthorized users to view private repository names via the 'Get a check run' API endpoint. This is an information disclosure vulnerability that exposes only repository names (not content) due to insufficient authorization checks on the API endpoint.

MitigationUpgrade GitHub Enterprise Server to version 3.17.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.0 or later to apply the vendor patch.

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

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

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

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

  1. Identify GitHub Enterprise Server version
    Navigate to the GitHub Enterprise Server admin interface, go to the Site Admin dashboard, or run 'ghe-version' from the command line if you have SSH access to the appliance.
    Affected if The installed version falls within any of these ranges: 3.7.0 to 3.7.18, 3.8.0 to 3.8.11, 3.9.0 to 3.9.6, or 3.10.0 to 3.10.3.
  2. Verify if GitHub Actions is enabled
    In the GitHub Enterprise Server admin settings, check under 'Actions' or 'Site admin' > 'Actions' to see if the Actions feature is enabled for the instance.
    Affected if GitHub Actions is enabled - the vulnerable API endpoint (Get a check run) is part of the Actions workflow system.
  3. Confirm presence of private repositories
    Review your GitHub Enterprise Server instance to confirm that private repositories exist on the platform.
    Affected if Private repositories are hosted on the affected GitHub Enterprise Server instance - these are the assets whose names could be exposed.
  4. Check for unauthorized API access logs
    Review GitHub Enterprise Server audit logs for API calls to the 'repos/{owner}/{repo}/check-runs/{check_run_id}' endpoint from users who do not have access to the referenced private repositories.

You are affected if your GitHub Enterprise Server version is 3.7.x below 3.7.19, 3.8.x below 3.8.12, 3.9.x below 3.9.7, or 3.10.x below 3.10.4, and you have GitHub Actions enabled with private repositories on the platform.

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 GitHub Enterprise Server to version 3.17.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.0 or later to apply the vendor patch.

Recommended fix High confidence

3.7.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.0 (or later)

  1. 1. Back up your GitHub Enterprise Server instance data and configuration before proceeding with any upgrade.
  2. 2. Review the GitHub Enterprise Server release notes for your target version to understand any known issues or migration requirements.
  3. 3. Upgrade your GitHub Enterprise Server to one of the fixed versions: 3.7.19, 3.8.12, 3.9.7, 3.10.4, or 3.11.0 (or later).
  4. 4. After upgrade, verify that the 'Get a check run' API endpoint properly enforces authorization and cannot be used to enumerate private repository names.
  5. 5. Test that existing functionality continues to work as expected after the upgrade.
Caveat Review release notes for your upgrade path; major version upgrades may have breaking changes requiring migration steps

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46646 — 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-46646 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