First published: Thu Aug 27 2020(Updated: )
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and was fixed in versions 2.21.6, 2.20.15, and 2.19.21. This vulnerability was reported via the GitHub Bug Bounty program.
Credit: product-cna@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitHub GitHub | <2.19.21 | |
GitHub GitHub | >=2.20.0<2.20.15 | |
GitHub GitHub | >=2.21.0<2.21.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-10517 is an improper access control vulnerability in GitHub Enterprise Server that allows authenticated users to determine the names of unauthorized private repositories.
CVE-2020-10517 affects GitHub Enterprise Server versions 2.19.21, 2.20.0 to 2.20.15, and 2.21.0 to 2.21.6.
CVE-2020-10517 has a severity rating of medium with a CVSS score of 4.3.
No, CVE-2020-10517 does not allow unauthorized access to any repository content, only the determination of unauthorized private repository names.
To fix CVE-2020-10517, update your GitHub Enterprise Server to version 2.19.22, 2.20.16, or 2.21.7.