CVE-2020-10517 Improper access control in GitHub Enterprise Server leading to the enumeration of private repository names

Medium 4.3 Published Updated

Authenticated users can enumerate private repository names via numerical IDs, exposing sensitive metadata without accessing content.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2020-10517?

CVE-2020-10517 is a medium-severity vulnerability in GitHub Enterprise Server, published on 27 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-285

Which versions are affected by CVE-2020-10517?

It affects 1 product.

Products include Github Github.

How do I fix CVE-2020-10517?

No fix has been published for CVE-2020-10517 yet. Limit exposure of the affected software until one is available.

Is CVE-2020-10517 being exploited?

There is no known exploitation of CVE-2020-10517 in the wild and no public exploit code.

Sources

Also known as GHSA-38rx-7wc7-6jvw.

Is CVE-2020-10517 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free