Cyber Resilience

CVE-2023-46646

Access Control in Github Enterprise Server 3.7.0 – 3.7.19

Access Control
Published
21 December 2023
Modified
16 December 2024
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0054 43th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-46646 is a medium-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Github Enterprise Server. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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

more

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.

CWE(s)
CWE-639

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-8447Same product: Github Enterprise Server
CVE-2026-3306Same product: Github Enterprise Server
CVE-2026-5845Same product: Github Enterprise Server
CVE-2023-22380Same product: Github Enterprise Server
CVE-2024-5746Same product: Github Enterprise Server
CVE-2024-5815Same product: Github Enterprise Server
CVE-2023-23760Same product: Github Enterprise Server
CVE-2024-1082Same product: Github Enterprise Server
CVE-2023-46645Same product: Github Enterprise Server
CVE-2026-5921Same product: Github Enterprise Server

Affected Assets

github
enterprise server
3.7.0 — 3.7.19 · 3.8.0 — 3.8.12 · 3.9.0 — 3.9.7

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

AC-24 Access Control Decisions
addresses: CWE-639

Per-request decision making makes it harder to bypass authorization using user-controlled keys without proper validation in the decision process.

AC-3 Access Enforcement
addresses: CWE-639

Consistent enforcement of approved authorizations makes bypassing via user-controlled keys ineffective.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.

PR.IR-01 mostly match
prevents

Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing authorization checks but does not prevent the weakness in production.

A.8.3 Information access restriction mostly match
prevents

Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.

A.5.15 Access control partial match
prevents

Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.

A.5.18 Access rights partial match
prevents

Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.

A.8.2 Privileged access rights partial match
mitigates

Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes authorization design but does not itself implement runtime access checks.

References