Learn about CVE-2020-10517, an improper access control vulnerability in GitHub Enterprise Server allowing authenticated users to enumerate unauthorized private repository names. Find out the impacted versions and mitigation steps.
An improper access control vulnerability in GitHub Enterprise Server allowed authenticated users to determine unauthorized private repository names. This CVE affected versions prior to 2.22 and was fixed in 2.21.6, 2.20.15, and 2.19.21.
Understanding CVE-2020-10517
This CVE involves an improper access control issue in GitHub Enterprise Server that could lead to the enumeration of private repository names.
What is CVE-2020-10517?
An improper access control vulnerability in GitHub Enterprise Server allowed authenticated users to identify unauthorized private repository names using their numerical IDs. This vulnerability did not grant access to any repository content beyond the name.
The Impact of CVE-2020-10517
The vulnerability affected all versions of GitHub Enterprise Server before 2.22. It was reported through the GitHub Bug Bounty program and was fixed in versions 2.21.6, 2.20.15, and 2.19.21.
Technical Details of CVE-2020-10517
This section provides technical details of the vulnerability.
Vulnerability Description
The vulnerability allowed authenticated users to determine unauthorized private repository names using their numerical IDs.
Affected Systems and Versions
Exploitation Mechanism
The vulnerability could be exploited by authenticated users to enumerate private repository names without proper authorization.
Mitigation and Prevention
Effective measures to mitigate and prevent the exploitation of this vulnerability.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates