Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2023-46646

Quick assessment

Affected
GitHub Enterprise Server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

GitHub Enterprise Server是美国GitHub开源的一个应用软件。提供一个将自己的GitHub实例设置为虚拟设备，从而提供可扩展，易于管理的平台。 GitHub Enterprise Server 3.7.0及更高版本存在安全漏洞，该漏洞源于存在访问控制错误漏洞，允许未经授权的攻击者通过Get a check run API端点查看私有存储库名称。

CVSS 5.3 · Medium EPSS 0.54% · P43

Possible ATT&CK Techniques 1 AI

T1530 · Data from Cloud Storage
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-46646

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5
Vulnerability Title
GitHub Enterprise Server 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
GitHub Enterprise Server是美国GitHub开源的一个应用软件。提供一个将自己的GitHub实例设置为虚拟设备，从而提供可扩展，易于管理的平台。 GitHub Enterprise Server 3.7.0及更高版本存在安全漏洞，该漏洞源于存在访问控制错误漏洞，允许未经授权的攻击者通过Get a check run API端点查看私有存储库名称。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
GitHub Enterprise Server 3.7.0 ~ 3.7.18 -

II. Public POCs for CVE-2023-46646

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-46646

请登录查看更多情报信息。

Other References for CVE-2023-46646 (4)

Same Patch Batch · GitHub · 2023-12-21 · 13 CVEs total

CVE-2023-46648 8.3 HIGH Insufficient Entropy in GitHub Enterprise Server Management Console Invitation Token
CVE-2023-6746 8.1 HIGH Sensitive Information in Log File in GitHub Enterprise Server
CVE-2023-46647 8.0 HIGH Improper Privilege Management in GitHub Enterprise Server management console leads to priv
CVE-2023-6847 7.5 HIGH Improper Authentication in GitHub Enterprise Server leading to Authentication Bypass for P
CVE-2023-6802 7.2 HIGH Sensitive Information in Log File in GitHub Enterprise Server
CVE-2023-46645 6.8 MEDIUM Path traversal in GitHub Enterprise Server leading to arbitrary file reading when building
CVE-2023-6804 6.5 MEDIUM Improper Privilege Management allows for arbitrary workflows to be run
CVE-2023-46649 6.3 MEDIUM Race Condition allows Administrative Access on Organization Repositories
CVE-2023-6803 5.8 MEDIUM Race Condition allows Unauthorized Outside Collaborator
CVE-2023-51379 4.9 MEDIUM Incorrect Authorization for Issue Comments in GitHub Enterprise Server
CVE-2023-6690 3.9 LOW GitHub Enterprise Server 安全漏洞
CVE-2023-51380 2.7 LOW Incorrect Authorization allows Read Access to Issue Comments in GitHub Enterprise Server

IV. Related Vulnerabilities

Same product: Enterprise Server
Same vendor: GitHub
Same weakness: CWE-639

V. Comments for CVE-2023-46646

No comments yet

Leave a comment