Home/CVE/An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization
CVE
CVE-2020-10516
An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization
An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21 and was fixed in 2.20.9, 2.19.15, and 2.18.20. This vulnerability was reported via the GitHub Bug Bounty program.
CRITICAL · CVSS 9.8
EPSS 0.0038
Schedule remediation
- CVSS base score ≥ 7.0
Sigma rules8
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2020-10516, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
20Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1003 · OS Credential Dumping T1005 · Data from Local System T1012 · Query Registry T1039 · Data from Network Shared Drive T1083 · File and Directory Discovery T1119 · Automated Collection T1134.001 · Token Impersonation/Theft T1213 · Data from Information Repositories T1530 · Data from Cloud Storage T1550.004 · Web Session Cookie T1552.001 · Credentials In Files T1552.002 · Credentials in Registry T1552.003 · Shell History T1552.004 · Private Keys T1552.006 · Group Policy Preferences T1555 · Credentials from Password Stores T1562.003 · Impair Command History Logging T1565.002 · Transmitted Data Manipulation T1574.005 · Executable Installer File Permissions Weakness T1574.006 · Dynamic Linker Hijacking
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLs CAPEC-CAPEC-104 · Cross Zone Scripting CAPEC-CAPEC-127 · Directory Indexing CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-150 · Collect Data from Common Resource Locations CAPEC-CAPEC-17 · Using Malicious Files CAPEC-CAPEC-39 · Manipulating Opaque Client-based Data Tokens CAPEC-CAPEC-402 · Bypassing ATA Password Security CAPEC-CAPEC-45 · Buffer Overflow via Symbolic Links CAPEC-CAPEC-5 · Blue Boxing CAPEC-CAPEC-51 · Poison Web Service Registry CAPEC-CAPEC-59 · Session Credential Falsification through Prediction
⬡
Weakness Classification
▤
Affected Products & Versions
3◈
Sigma Hunt Rules
8Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
producthighGithub Push Protection Disabled
producthighGithub Secret Scanning Feature Disabled
producthighGithub High Risk Configuration Disabled
productmediumGithub Repository/Organization Transferred
productmediumGithub SSH Certificate Configuration Changed
productmediumGithub Fork Private Repositories Setting Enabled/Cleared
▣
Scoring & Timeline
9.8
CRITICAL · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.